After OCP code/feature freeze, update the CMO resource reference: monitoring-resources-reference-for-the-cluster-monitoring-operator.adoc content from the CMO repo and add the new content to the OCP docs.

Description of tasks:

For every release, the Asciidoc content for Resources reference for the Cluster Monitoring Operator should be updated in the core OCP docs. This content is automatically generated from code comments and aggregated into resources.adoc

For every release, the writer needs to do the following things to update the OCP docs .adoc file:

1. During dev work for changes and additions to the CMO code, edit any changes or additions to the source code comments that engineers have made in the CMO (work with engineers to scope this work and track it in separate Jira issues).
2. Diff the changes from the previous release and update the config map reference Asciidoc file (monitoring-resources-reference-for-the-cluster-monitoring-operator.adoc) that is included in the core OCP docs. The easiest way to do this is to check out the CMO source code from the Github repository and fetch all the upstream release branches, and then diff the changes in resources.adoc between the previous release branch and the current release branch:
   • Example:
     $ git diff release-4.16 release-4.17 Documentation/resources.adoc
     to show all the new and updated content for resources.adoc between the 4.16 and 4.17 releases of the CMO.
3. Create a feature branch for the OCP docs repo that incorporates the changes from the diff into the config map reference asciidoc file for the core OCP docs.
4. Create a PR in the OCP docs repo to add the changes only to the main branch and the branch for the 4.1x release.