Designate nodes for hosting control-plane to avoid charging

Create an informative issue (See each section, incomplete templates/issues won't be triaged)

Using the current documentation as a model, please complete the issue template.

Note: Doc team updates the current version and the two previous versions (n-2). For earlier versions, we will address only high-priority, customer-reported issues for releases in support.

Prerequisite: Start with what we have

Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 3:

• Use the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.6

• Use the GitHub link to find the staged docs in the repository: https://github.com/stolostron/rhacm-docs

  Describe the changes in the doc and link to your dev story

Provide info for the following steps:

1. - [X] Mandatory Choose the documentation release (Published releases are refreshed ~weekly after publication).

• [ ] ACM 2.5
• [ ] ACM 2.6
• [ ] ACM 2.7
• [X]ACM 2.8 (upcoming release)

• [ ] MCE 2.1
• [ ] MCE 2.2
• [X] MCE 2.3 (upcoming release)

2. - [x] Mandatory Choose the type of documentation change.

• [x] New topic in an existing section or new section
• [ ] Update to an existing topic

3. - [x] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation: https://hypershift-docs.netlify.app/how-to/distribute-hosted-cluster-workloads/

4. - [X] Mandatory for GA content:

• [x] Add steps and/or other important conceptual information here: The steps to achieve this today would be:
  Label workers in management cluster regular OCP.
  Express intent for distributing workloads as in https://hypershift-docs.netlify.app/how-to/distribute-hosted-cluster-workloads/
  The remaining blocker task here is to document all the above together 
  Also we should exercise the above in CI.

• [ ] Add Required access level for the user to complete the task here:

• [ ] Add verification at the end of the task, how does the user verify success (a command to run or a result to see?)

• [ ] Add link to dev story here: