OBSDOCS-3154: Add namespace and managementState to TempoStack forwarding example

[kruthi9]

Summary

• Fixes OBSDOCS-3154 in the Forwarding traces to a TempoStack instance example.
• Adds namespace: otel-collector-example to the ServiceAccount and OpenTelemetryCollector examples so they match the existing ClusterRoleBinding.
• Adds spec.managementState: managed to the OpenTelemetryCollector CR to resolve the console YAML schema error (Missing property "managementState").

Test plan

• Confirm the updated YAML in modules/otel-forwarding-traces.adoc pastes into the OpenShift console without schema errors
• Confirm namespace values are consistent across ServiceAccount, ClusterRoleBinding, and OpenTelemetryCollector
• Preview the Forwarding telemetry assembly if applicable

[openshift-ci-robot]

@kruthi9: This pull request references OBSDOCS-3154 which is a valid jira issue.

Details

In response to this:

Summary

• Fixes OBSDOCS-3154 in the Forwarding traces to a TempoStack instance example.
• Adds namespace: otel-collector-example to the ServiceAccount and OpenTelemetryCollector examples so they match the existing ClusterRoleBinding.
• Adds spec.managementState: managed to the OpenTelemetryCollector CR to resolve the console YAML schema error (Missing property "managementState").

Test plan

• Confirm the updated YAML in modules/otel-forwarding-traces.adoc pastes into the OpenShift console without schema errors
• Confirm namespace values are consistent across ServiceAccount, ClusterRoleBinding, and OpenTelemetryCollector
• Preview the Forwarding telemetry assembly if applicable

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hi @kruthi9. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.