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

The troubleshooting documentation and the installation guide cover uninstalling and cleanup, e.g.

• https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html-single/install/index#removing-a-multiclusterhub-instance-by-using-commands step 4 and https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html-single/troubleshooting/index#resolving-the-problem-reinstallation-failure step 4 as well have the same content. The script section is what I am focussing on.

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

We just need to add in the commands the deletion of the local-cluster namespace. If it remains, it will block attempts to reinstall.

it may be good to also put a note to not delete the namespaces of clusters that are not detached as well - those can be re-imported if you reinstall.

Provide info for the following steps:

1. - [X] 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

3. - [ ] Mandatory for GA content:
            
       - [ ] Add steps and/or other important conceptual information here: 
       
            
       - [ ] 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:

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