Revise Entra report header with new exclusion info and documentation name

[schrolla]

🗣 Description

Changes the header in the CreateReport.psm1 module that generates the header of the Entra HTML report so no longer references the README file, but rather the overall documentation. Also adds a sentence to better explain what an exclusion is and why it is useful.

💭 Motivation and context

The Entra report should provide up-to-date and accurate information for users to understand their options and point to the current documentation.

Closes #1457

🧪 Testing

Run Invoke-SCuBA -p aad with valid credentials to generate an Entra HTML report. View the report and verify that the new language is visible, correct, and the new link works.

✅ 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.
• 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.
• Unit tests added/updated to cover PowerShell and Rego changes.
• Functional tests added/updated to cover PowerShell and Rego changes.
• All relevant functional tests passed.
• 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

• 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.

[tkol2022]

Slightly tweaked the first sentence so that it matches up with the language we have in the config file documentation. Also we don't support exclusions for roles. Only users and groups can be excluded from policies.
Nice work.

[ehaines1]

Everything works as expected

[schrolla]

@nanda-katikaneni This PR is ready for merge.