Add forward and backward references for the Azure Firewall Policy to lookup the Firewall Policy Rule Collection Group. This is required for the FinopsPolicy so that it can check if there are application rules associated with the Firewall Policy

Fixes two issues with the `dependency_paths` logic

* Adds wildcard suffix to the generated `dependency_paths` for autodetect. This
is done so that changes in nested files are detected on Infracost's hosted services.
* Merges the tfvars into the `DependencyPaths` method, this resolves an issue where
if no module calls were detected then only tfvars would be added to the `dependency_paths`
config key. This would omit the project from the changes and therefore only tfvar changes
would cause a rerun on hosted services. This also standardises things for those users
who use a template, as now the tfvars are part of the `.DependencyPaths` project template
variable.

This flag expects a file with markdown comment content to post it to the
PR/commit. When this flag is provided the --path flag is not needed.

Resolves issue where the parser variables where being marshalled to a
map for each `walkPath` call. This would cause an OOM for large repositories.

…3105)

Pattern matching doesn't work for the tfvar dependency paths when
they're relative but works okay when they're relative to the starting
path like module calls

v1.26 is on extended support since June 11th 2024.

* refactor: add `region` field to resource data

Adds a `Region` property to the `schema.ResourceData` which is set when
parsing the plan and set before evaluating each individual resource. This
property is meant to replace the old `d.Get` approach which sets the region
directly on the `RawValues` of the json.

This new approach sets the `Region` after the references have been parsed and
changes the `azure` region functionality to use the `getLocation` logic that was
previously done on demand per resource.

* refactor: add `GetRegion` func to `RegistryItem`

Adds a resource specific `GetRegion` property to the `RegistryItem` which
can be used to override the provider default functionality for fetching a
region for a resource.

Changes usage of `lookupRegion` functions in azure resources to use the new
`ResourceData.Region` property which is computed before evaluation.

Changes the `ResourceRegistryMap` to no longer use a `sync.Once` and instead be
built as a singleton `var`. This removes the sync requirement as callers only read
from this map.

* fix: recursively set the reference region if they are not already set

…3108)

* enhance: Make --comment-path flag optional keeping --path required

Without infracost.json validAt timestamp is missing that can lead to
posting stale comments if `infracost comment` is run simultaneously.

* fixup! enhance: Make --comment-path flag optional keeping --path required

Adds support for more resources to use the `GetRegion` method, also changes
the signature of the method so that it we fetch the default region first and
pass this to the more specific resource function.

Update the DynamoDB resource to read the `point_in_time_recovery` block
to ensure that it is enabled so PITR costs aren't inadvertently added to
the cost estimate.

Add test to validate

* enhance: Update PR comment's cost change summary

* feat: Rename Cost details to Estimate details in PR comment

* feat: Remove 'View report' link from PR comment

Keeping .Root.CloudURL as it's used for Bitbucket as it doesn't support
collapsed sections.

* feat: Do not show Usage cost values when usage costs are disabled

* fixup! feat: Do not show Usage cost values when usage costs are disabled

* fixup! fixup! feat: Do not show Usage cost values when usage costs are disabled

* chore: Update tests

* chore: Update AWS tests

* chore: Update Azure tests

* chore: Update Google tests

* fixup! chore: Update tests

* fixup! chore: Update AWS tests

* fixup! chore: Update AWS tests

* fixup! fixup! feat: Do not show Usage cost values when usage costs are disabled