feat(traits): remove deprecated logging, master and telemetry traits

docs/modules/ROOT/nav.adoc

@@ -65,8 +65,6 @@
 ** xref:traits:keda.adoc[Keda]
 ** xref:traits:knative-service.adoc[Knative Service]
 ** xref:traits:knative.adoc[Knative]
-** xref:traits:logging.adoc[Logging]
-** xref:traits:master.adoc[Master]
 ** xref:traits:mount.adoc[Mount]
 ** xref:traits:owner.adoc[Owner]
 ** xref:traits:pdb.adoc[Pdb]
@@ -76,7 +74,6 @@
 ** xref:traits:route.adoc[Route]
 ** xref:traits:security-context.adoc[Security Context]
 ** xref:traits:service.adoc[Service]
-** xref:traits:telemetry.adoc[Telemetry]
 ** xref:traits:toleration.adoc[Toleration]
 // End of autogenerated code - DO NOT EDIT! (trait-nav)
 * xref:kamelets/kamelets.adoc[Kamelets]

docs/modules/ROOT/pages/troubleshooting/troubleshooting.adoc

@@ -11,7 +11,7 @@ Most of the time, your Integration build cycle runs fine. Then a Deployment and
 
 First of all, you need to try to check the log of the application. Try using `kamel logs test` or `kubectl logs test-7856cb497b-smfkq`. If there is some problem within your Camel application, you will typically discover it at runtime only. Checking the logs and understanding the reason of the failure there should be the easiest approach.
 
-NOTE: use logging trait to change the level of log, if needed.
+NOTE: use the `quarkus.log.level` property to change the level of log, if needed (ie, `kamel run test.yaml -p quarkus.log.level=DEBUG`).
 
 [[troubleshoot-integration-cr]]
 == Checking Integration custom resource

docs/modules/ROOT/partials/apis/camel-k-crds.adoc

@@ -6215,14 +6215,18 @@ The configuration of Knative Service trait
 |
 
 
-The configuration of Logging trait
+The configuration of Logging trait.
+
+Deprecated: no longer in use.
 
 |`master` +
 *xref:#_camel_apache_org_v1_trait_MasterTrait[MasterTrait]*
 |
 
 
-The configuration of Master trait
+The configuration of Master trait.
+
+Deprecated: no longer in use.
 
 |`mount` +
 *xref:#_camel_apache_org_v1_trait_MountTrait[MountTrait]*
@@ -6335,7 +6339,9 @@ Deprecated: no longer in use.
 |
 
 
-The configuration of Telemetry trait
+The configuration of Telemetry trait.
+
+Deprecated: no longer in use.
 
 |`toleration` +
 *xref:#_camel_apache_org_v1_trait_TolerationTrait[TolerationTrait]*
@@ -8684,11 +8690,12 @@ If this is true, the created Knative trigger uses the event type as a filter on
 
 * <<#_camel_apache_org_v1_Traits, Traits>>
 
+WARNING: This trait is no longer in use.
+
 The Logging trait is used to configure Integration runtime logging options (such as color and format).
 The logging backend is provided by Quarkus, whose configuration is documented at https://quarkus.io/guides/logging.
 
-WARNING: The Logging trait is **deprecated** and will be removed in future release versions:
-use Quarkus logging properties directly instead.
+The Logging trait was removed: use Quarkus logging properties directly instead.
 
 Migration example:
 
@@ -8753,6 +8760,8 @@ Enable "pretty printing" of the JSON logs
 
 * <<#_camel_apache_org_v1_Traits, Traits>>
 
+WARNING: This trait is no longer in use.
+
 The Master trait allows to configure the integration to automatically leverage Kubernetes resources for doing
 leader election and starting *master* routes only on certain instances.
 
@@ -8761,10 +8770,9 @@ It's activated automatically when using the master endpoint in a route, e.g. `fr
 NOTE: this trait adds special permissions to the integration service account in order to read/write configmaps and read pods.
 It's recommended to use a different service account than "default" when running the integration.
 
-WARNING: The Master trait is **deprecated** and will be removed in future release versions.
-This trait requires the operator to manage RBAC explicitly, which should be avoided for security
-and simplicity reasons. Users should manually create the required Role and RoleBinding, then configure
-Quarkus properties directly:
+The Master trait was removed: it required the operator to manage RBAC explicitly, which should be
+avoided for security and simplicity reasons. Users should manually create the required Role and
+RoleBinding, then configure Quarkus properties directly:
 
 	-p quarkus.camel.cluster.kubernetes.resource-name=<integration>-lock
 	-p quarkus.camel.cluster.kubernetes.resource-type=Lease
@@ -9707,22 +9715,22 @@ Don't use in Knative based environments.
 
 * <<#_camel_apache_org_v1_Traits, Traits>>
 
+WARNING: This trait is no longer in use.
+
 The Telemetry trait can be used to automatically publish tracing information to an OTLP compatible collector.
 
 The trait is able to automatically discover the telemetry OTLP endpoint available in the namespace (supports **Jaerger** in version 1.35+).
 
 The Telemetry trait is disabled by default.
 
-WARNING: The Telemetry trait is **deprecated** and will be removed in future release versions.
-The same behavior can be achieved via properties and dependencies configuration.
+The Telemetry trait was removed: the same behavior can be achieved via properties and
+dependencies configuration.
 
 Migration example:
 
 	Before: --trait telemetry.endpoint=http://jaeger:4317
 	After:  -p quarkus.otel.exporter.otlp.traces.endpoint=http://jaeger:4317
 
-WARNING: The Telemetry trait can't be enabled at the same time as the Tracing trait.
-
 
 [cols="2,2a",options="header"]
 |===