Drop 2.9 deprecated traits

[squakez]

Requirement

Remove from the codebase the already deprecated traits:

• logging
• master
• telemetry

[hxxxi-malog]

Hi, I'd like to work on this issue if no one else has started yet. 🙂

I've looked into the codebase, and my plan would be:

1. API definitions: remove LoggingTrait, MasterTrait and TelemetryTrait from pkg/apis/camel/v1/trait/ and drop the corresponding fields from the Traits struct in common_types.go.
2. Trait implementations: remove pkg/trait/{logging,master,telemetry}.go and their unit tests, and unregister them in trait_register.go.
3. Generated code / CRDs: re-run make generate to refresh the generated deepcopy functions, apply configurations, trait descriptions (zz_desc_generated.go, zz_generated_doc.go) and the CRD manifests in pkg/resources/config/crd/bases/ (integrations, pipes, integrationplatforms, integrationprofiles).
4. Tests: update tests that still reference these traits (e.g. trait_configure_test.go, platform/defaults_test.go, cmd/run_test.go), and remove the related e2e tests (e2e/common/traits/master_test.go, e2e/telemetry/).
5. Docs: remove docs/modules/traits/pages/{logging,master,telemetry}.adoc and their navigation entries.

Since all three traits were deprecated in 2.9.0 with migration paths already documented (Quarkus properties / manual Role+RoleBinding for master), this looks like a clean removal for the 2.12.0 milestone. Happy to adjust the plan if maintainers prefer a different scope.

[squakez]

Thanks for taking care. I'll have a look at the PR soon. However, point 1 (API definition) is not correct. We must keep the API for compatibility reason. We just need to comment with a //Deprecated: no longer in use wherever those API are referenced in the code. CRD should not change at all.

[hxxxi-malog]

Thanks for taking care. I'll have a look at the PR soon. However, point 1 (API definition) is not correct. We must keep the API for compatibility reason. We just need to comment with a //Deprecated: no longer in use wherever those API are referenced in the code. CRD should not change at all.

Thank you for your suggestions and review. Based on your suggestions, I re-reviewed my changes in this revision. The pull request already follows that approach: the API types and spec.traits fields retain their original JSON names, marked as // Deprecated: no longer used. (Renamed with a Deprecated* prefix, following the same convention as the Jolokia removal in #6766.) The CRD schema is unaffected; the only CRD diff is the “Deprecated: no longer used.” description text, which controller-gen derives based on the new comments (as was also done in #6766). If you would prefer the CRD bytes to be exactly identical, I would also be happy to resubmit the description text.