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 4:

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

 - 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. - [ ] Mandatory Add the required version to the Fix version/s field.

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

      - [ ] New topic in an existing section or new section
      - [x] Update to an existing topic https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.8/html/governance/governance#configure-concurrency

3. - [x] Mandatory for GA content:
            
       - [x] Add steps and/or other important conceptual information here:

In the sections that describe configuring controller concurrency (2.4.1), QPS (2.4.2), and burst (2.4.2), the `ManagedClusterAddon` objects that reference `goverance-policy-framework` addon controllers should also be included. These options can be set the same way as how the current `config-policy-controller` is configured to do so, using annotations on the `ManagedClusterAddon` objects to override the default values. The default values for `policy-evaluation-concurrency` is 2, for `client-qps` is 30, and for `client-burst` is 45, same as the default values for `config-policy-controller`. Currently, there is interest to independently configure QPS and Burst for the hub cluster client and managed cluster client, so I will provide updates in the comments as the story progresses.
            
       - [ ] Add Required access level for the user to complete the task here:
       

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

The `governance-policy-framework` pod on the managed cluster should have arguments matching the configured values. For example, if the queries per second was configured to be 75, `--client-max-qps=75` would be present in the pod YAML.

       - [x] Add link to dev story here: https://issues.redhat.com/browse/ACM-6711

4. - [ ] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation: