Fix #6829: drop support for kamel run --dev/--sync

[Suhail98]

Fixes #6829

kamel run --dev and --sync were deprecated in v2.9.0 and printed a removal notice on every use. This removes them, so kamel run no longer carries a file-watching rebuild loop that nothing else in the CLI depends on.

What is removed

• The --dev and --sync flags and the Dev / Sync fields on runCmdOptions.
• The --dev + -o/--output mutual-exclusion check and the "Dev and Sync properties are deprecated" notice in validate.
• In run: the SIGTERM handler that deleted the Integration on Ctrl-C, and the o.Dev / o.Sync arms of the --logs and --wait conditions.
• syncIntegration, plus what only it used: filterFileLocation (run_support.go), the pkg/util/sync package, and DeleteIntegration (pkg/cmd/util.go). The e2e suite has its own DeleteIntegrations in e2e/support, so nothing else calls it.
• The unit tests covering the two flags, and TestFilterFileLocation.

--logs and --wait behave exactly as before: the two if o.Logs branches left after the o.Dev arms were dropped are merged into one, which is the same sequence of calls in the same order.

No deprecation shim is added — Cobra already answers --dev with unknown flag: --dev, matching how #6816 left the removed subcommands. Following your reviews on #6807 and #6816, there is also no test asserting the flags are gone.

The only mention left in docs/ was a passing "dev mode" aside in configuration/dependencies.adoc; it is reworded rather than deleted, since the point it makes about automatic dependency resolution still holds.

Testing

go build ./pkg/... ./cmd/..., go vet ./pkg/cmd/... ./pkg/util/... and gofmt -l are clean, and go test ./pkg/cmd/... shows the same 10 pre-existing Windows-only path/file-lock failures before and after the change. Built ./cmd/kamel and confirmed --dev and --sync are gone from run --help and now report unknown flag.

[squakez]

Cool cleaning work. Thanks. A few comments to verify.

[github-actions]

✔️ Unit test coverage report - coverage increased from 63.9% to 64.2% (+0.3%)

[github-actions]

✔️ Unit test coverage report - coverage increased from 63.8% to 64.2% (+0.4%)

[squakez]

Please, make lint-fix or the needed to fix the linting problems reported.

[Suhail98]

Both lint issues fixed, and both turned out to be fallout from the removal rather than formatting noise:

• gosec G118 in root.go — syncIntegration held the only call to RootCmdOptions.ContextCancel, so once it was gone the cancel func from WithCancel was never called. The child context only existed so sync could cancel and restart the in-flight command, so I dropped it, along with RootContext, whose single remaining use was the <-o.RootContext.Done() wait point in run. That now waits on o.Context, which is the same instant: the child was only ever cancelled by its parent. Shout if you'd rather keep the fields and silence the linter instead.
• tagalign in run.go — the removed Sync / Dev fields left the surrounding tags ragged. Realigned.

No make on my machine, so I ran the pinned linter directly: golangci-lint v2.13.2 run --config .golangci.yml. Clean apart from 12 mnd reports in files listed under mnd.ignored-files — those paths use forward slashes, so the ignore list doesn't match on Windows. Nothing there is touched by this PR.