[enterprise-4.14] OBSDOCS-1629: Flatten the Distributed tracing docs structure

[max-cx]

Version(s): OCP 4.14

Issue: https://issues.redhat.com/browse/OBSDOCS-1629

Link to docs preview: See #92944

QE review: N/A

Additional information: Cherry-pick of #92944

[openshift-ci-robot]

@max-cx: This pull request references OBSDOCS-1629 which is a valid jira issue.

In response to this:

Version(s):

Issue:

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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-robot]

@max-cx: This pull request references OBSDOCS-1629 which is a valid jira issue.

In response to this:

Version(s): OCP 4.14

Issue: https://issues.redhat.com/browse/OBSDOCS-1629

Link to docs preview: See #92944

QE review: N/A

Additional information: Cherry-pick of #92944

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.

[max-cx]

/retest

[max-cx]

/test

[openshift-ci]

@max-cx: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test validate-asciidoc

/test validate-portal

Use /test all to run all jobs.

In response to this:

/test

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.

[max-cx]

/test all

[openshift-ci]

@max-cx: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/validate-asciidoc	4f0baa8	link	true	/test validate-asciidoc

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.