GitHub PAT requires too many permissions

### Community Note

- Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment

### Description

My customer is concerned with the amount of permissions that the GitHub PAT requires and is specifically concerned with the ```admin:org``` and ```delete_repo``` permissions. They decided to deploy manually using the ```-c local``` option

**Describe the solution you'd like**

Provide options for the customer.

- I believe that the ```delete_repo``` is only required for a ```terraform destroy``` command. We could mention that it is optional in the documentation.
- For the ```admin:org``` option, modify the accelerator to use an existing approval team if it already exists. Then provide instructions to the customer as to how to create the team manually themselves.

**Additional context**

Start by reviewing the GitHub PAT permission requirements for the accelerator and the -c local deployment path. Verify whether delete_repo is needed only for terraform destroy, then assess reuse or manual creation of an admin:org approval team. Done means customers have clearly documented least-privilege options and the accelerator behavior matches them.

Written by the indexing model from the issue text.