Fix GitHub issue #32713: update the new logging operator name

[lbscorpio]

@vikram-redhat This PR is to fix the issue#32713, minimum version that the change applies to should be 4.7 in my opinion, could you arrange someone to review them? Thanks.

Major changes on my commit:

1. modules/cluster-logging-deploy-console.adoc
   On the Custom Resource Definition Overview page -> On the Custom Resource Definition details page(verified with the OCP 4.7.11)
2. modules/cluster-logging-updating-logging.adoc
   Verify that the Cluster Logging Operator version is 5.0.x. -> Only changed this name to Red Hat OpenShift Logging on this file, because operator name will be changed after upgrading.
3. All other Cluster Logging (only Operator name, not CR name) changed to Red Hat OpenShift Logging
4. File name clo-xx.yaml change to olo-xx.yaml, because the operator name is changed so the short name can be changed.

[netlify]

Deploy Preview for osdocs ready!

Built with commit 5ce6cb7

https://deploy-preview-32726--osdocs.netlify.app

[rolfedh]

/lgtm

[Preeticp]

/cherrypick enterprise-4.7

[Preeticp]

/cherrypick enterprise-4.8

[openshift-cherrypick-robot]

@Preeticp: #32726 failed to apply on top of branch "enterprise-4.7":

Applying: Fix GitHub issue #32713: update the new logging operator name
Using index info to reconstruct a base tree...
M	logging/cluster-logging-deploying.adoc
M	modules/cluster-logging-about-crd.adoc
M	modules/cluster-logging-collector-log-forward-es.adoc
M	modules/cluster-logging-collector-log-forwarding-about.adoc
M	modules/cluster-logging-deploy-cli.adoc
M	modules/cluster-logging-deploy-console.adoc
M	modules/cluster-logging-deploying-about.adoc
M	modules/cluster-logging-updating-logging.adoc
M	modules/dedicated-cluster-install-deploy.adoc
M	modules/gathering-data-specific-features.adoc
M	modules/infrastructure-moving-logging.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/infrastructure-moving-logging.adoc
Auto-merging modules/gathering-data-specific-features.adoc
Auto-merging modules/dedicated-cluster-install-deploy.adoc
Auto-merging modules/cluster-logging-updating-logging.adoc
Auto-merging modules/cluster-logging-deploying-about.adoc
Auto-merging modules/cluster-logging-deploy-console.adoc
Auto-merging modules/cluster-logging-deploy-cli.adoc
CONFLICT (content): Merge conflict in modules/cluster-logging-deploy-cli.adoc
Auto-merging modules/cluster-logging-collector-log-forwarding-about.adoc
Auto-merging modules/cluster-logging-collector-log-forward-es.adoc
Auto-merging modules/cluster-logging-about-crd.adoc
Auto-merging logging/cluster-logging-deploying.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Fix GitHub issue #32713: update the new logging operator name
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick enterprise-4.7

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/test-infra repository.

[openshift-cherrypick-robot]

@Preeticp: #32726 failed to apply on top of branch "enterprise-4.8":

Applying: Fix GitHub issue #32713: update the new logging operator name
Using index info to reconstruct a base tree...
M	logging/cluster-logging-deploying.adoc
M	logging/cluster-logging-external.adoc
M	modules/cluster-logging-about-crd.adoc
M	modules/cluster-logging-deploy-cli.adoc
M	modules/cluster-logging-deploy-console.adoc
M	modules/cluster-logging-deploying-about.adoc
M	modules/cluster-logging-updating-logging.adoc
M	modules/dedicated-cluster-install-deploy.adoc
M	modules/gathering-data-specific-features.adoc
M	modules/infrastructure-moving-logging.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/infrastructure-moving-logging.adoc
Auto-merging modules/gathering-data-specific-features.adoc
Auto-merging modules/dedicated-cluster-install-deploy.adoc
Auto-merging modules/cluster-logging-updating-logging.adoc
Auto-merging modules/cluster-logging-deploying-about.adoc
Auto-merging modules/cluster-logging-deploy-console.adoc
Auto-merging modules/cluster-logging-deploy-cli.adoc
CONFLICT (content): Merge conflict in modules/cluster-logging-deploy-cli.adoc
Auto-merging modules/cluster-logging-about-crd.adoc
Auto-merging logging/cluster-logging-external.adoc
Auto-merging logging/cluster-logging-deploying.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Fix GitHub issue #32713: update the new logging operator name
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick enterprise-4.8

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/test-infra repository.

[rolfedh]

I'll manually CP these changes into 4.7 and 4.8 later this week: https://issues.redhat.com/browse/RHDEVDOCS-3025