Cleaning up and streamlining config files

[amart241]

Cleaning up and streamlining config files

🗣 Description

I have formatted the sample config files to be more streamlined. I have also added the other EntraID exclusions that are now available for AAD

💭 Motivation and context

The sample configs have been updated and not streamlined in a while and needed a refresh.
I removed extra references to other baselines in baseline specific sample files and added a more detailed and standardized description. This resolves #1075

🧪 Testing

Sample config files no code was changed

✅ 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 a single goal - eschew scope creep!
• Changes are sized such that they do not touch excessive number of files.
• 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 automated checks (e.g., linting, static analysis, unit/smoke tests) passed.

✅ 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

✅ 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]

The previous config files are referenced in the new-and-improved readme. Please read through the readme to make sure that the documentation is still accurate. ATM, you can find this on the 877 branch:
https://github.com/cisagov/ScubaGear/tree/877-streamline-the-docs
Look in /docs/configuration/configuration.md
Thanks!

[schrolla]

@amart241 The pre-approval section of the checklist is not complete and the ones that are checked, I would argue, are not complete since the PR title doesn't yet reflect a human-readable title (still the default) and the branch has not yet been rebased against main. Recommend completing the pre-approval checklist and then re-requesting reviews at that time.

[schrolla]

@amart241 Any updates on this PR? It's been in "New" state with no updates for a month.

[amart241]

@amart241 Any updates on this PR? It's been in "New" state with no updates for a month.

Just got back this week from being sick and lots of trips. Working on this afternoon to get this resolved.

[schrolla]

Re-reviewed and recommending a number of misspelling clean ups and clarifications. See below for details.

[schrolla]

Looks good after updates.

[buidav]

Approving as the original issue was just to clean up the original config files.

However, I'm noticing how confusing our current documentation is and how the sample config file examples spread the currently available syntax for setting per product exclusions and omissions into multiple different files.

Created #1254 to create one unified file someone can look at to understand all the possible config file values they have to fill in order to pass certain policy checks for Dender and/or AAD and how to do policy omissions.

[schrolla]

@nanda-katikaneni This PR is ready for merge.