fix: autoinclude config path fixes (#6711)

* chore: autoinclude config path fixes

* chore: autoinclude cleanup

* chore: tests simplification

* chore: partial merge fix

* fix: Adjust fix in #6711 so that it uses the autoinclude decode order instead of ignoring errors

* chore: retrigger CI after macOS lint module-download flake

The previous run failed lint on macos due to a transient
proxy.golang.org error fetching charmbracelet/ultraviolet,
which skipped base_tests and integration_tests.

---------

Co-authored-by: Yousif Akbar <11247449+yhakbar@users.noreply.github.com>

Author: denis256

docs/src/data/changelog/v1.1.4/autoinclude-config-path-override.mdx

@@ -0,0 +1,10 @@
+---
+version: "v1.1.4"
+category: "bug-fixes"
+---
+
+#### Autoinclude dependency overrides no longer evaluate replaced paths
+
+Terragrunt used to evaluate a dependency's original `config_path` before applying a sibling autoinclude override. This could prevent a unit from being parsed when the original path referenced a value that the unit no longer supplied, even though the autoinclude replaced that path. Terragrunt now leaves replaced dependency blocks undecoded, then applies the autoinclude override. Dependency blocks without an autoinclude override are still validated.
+
+Blocks that use `expansion` are still decoded, because a bare autoinclude label does not name their instances. If the autoinclude also declares the same label without expansion, Terragrunt reports a dependency label collision.