alignment with AVM specification & grept-apply requirements

[kewalaka]

Description

This re-aligns the template with changes to the docs / AVM specification & fixes reported by grept-apply.

There are some existing PRs which repeat the same functionality, adding tags & new files to .gitignore based on grept-apply outputs, I believe this is more comprehensive (cc @jaredfholgate for a check)

It introduces the fix for private endpoints conflicting with Azure Policy based on the spec, with some corrections raised with @matt-FFFFFF here; Azure/terraform-azurerm-avm-res-keyvault-vault#32 (comment)

I've used this as the starting point for the SQL Module that I'm preparing to post, as you can't properly lint this code due to things like TODOs.

-->

Type of Change

• Non-module change (e.g. CI/CD, documentation, etc.)
• Azure Verified Module updates:
  • Bugfix containing backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in locals.version.tf.json:
    • Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
    • The bug was found by the module author, and no one has opened an issue to report it yet.
  • Feature update backwards compatible feature updates, and I have bumped the MINOR version in locals.version.tf.json.
  • Breaking changes and I have bumped the MAJOR version in locals.version.tf.json.
  • Update to documentation

Checklist

• I'm sure there are no other open Pull Requests for the same update/change (there are some minors - noted above).
• My corresponding pipelines / checks run clean and green without any errors or warnings
• I did run all pre-commit checks

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Note

This label was added as per ITA06.

[kewalaka]

this also includes the fix for the location / "evil data source" 😅

[jaredfholgate]

LGTM