Update ScubaGear authentication documentation for additional GCC High, Defender, and SharePoint details

[buidav]

🗣 Description

• This PR updates our documentation relating to multiple small but related authentication things.
  • Adds documentation for details necessary for ScubaGear non-interactive auth in GCC High
  • 'Lowers' the necessary interactive auth role from SharePoint admin to Global Reader
  • 'Lowers' the MS Graph permission noted in SharePoint non-interactive auth to Organization.Read.All as noted from Create a JSON file to store permission scopes required for ScubaGear #1380
  • Adds an explanation for why we include permissions with bundled in write privileges to our non-interactive permissions table.
  • Also fixed some extra white space stuff. I saw from a custom extension.

💭 Motivation and context

Closes #265
Closes #1555
Closes #1556

🧪 Testing

• Screenshots and explanations are located in the various issues being closed by this PR.
• Testing was done by assigning SPs or creating new user accounts to authenticate into our Tests tenants.
• Reviewers are not meant to recreate all of the experiments noted in those issues from scratch. Just check that the language added to the documentation is good and accurate.

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• PR targets the correct parent branch (e.g., main or release-name) for merge.
• Changes are limited to single related goals - eschew scope creep!
• Changes are sized such that they do not touch excessive number of files.
• All future TODOs are captured in issues, which are referenced in code comments.
• These code changes follow the ScubaGear content style guide.
• Related issues these changes resolve are linked preferably via closing keywords.
• All relevant type-of-change labels added.
• All relevant project fields are set.
• All relevant repo and/or project documentation updated to reflect these changes.

✅ Pre-merge checklist

• PR passed smoke test check.

• Feature branch has been rebased against changes from parent branch, as needed

  Use Rebase branch button below or use this reference to rebase from the command line.

• Resolved all merge conflicts on branch

• Notified merge coordinator that PR is ready for merge via comment mention

• N/A Demonstrate changes to the team for questions and comments.
  (Note: Only required for issues of size Medium or larger)

✅ Post-merge checklist

• Feature branch deleted after merge to clean up repository.
• Verified that all checks pass on parent branch (e.g., main or release-name) after merge.

[james-garriss]

Some opportunities for grammar and clarification improvements (see below), but nothing critical. Approved.

NOTE: I only reviewed the documentation. I did not attempt to run and test ScubaGear with the permission changes.

[tkol2022]

I made some tweaks. I wanted to point out that the name of the respective M365 application is missing from the permissions table in the noninteractive.md file, but Microsoft is adding that with their upcoming PR so we don't have to worry about that right now. I put a screenshot of their table with the new API NAME and API APPID columns for reference.

[buidav]

@nanda-katikaneni this is ready to merge