Backport of Handle move blocks within a module which is changing the index into v1.1

[teamterraform]

Backport

This PR is auto-generated from #30232 to be assessed for backporting due to the inclusion of the label 1.1-backport.

The below text is copied from the body of the original PR.

---

When a move statement is only changing the index of a module, any moves within that module would result in cycles, because both the absolute From and To addresses would match both of the parent module's From and To address.

For example, changing the index of a module named count results in a a from->to of:

module.count->module.count[0]

And changing the count of a resource nested within module.count results in:

module.count[*].test.count->module.count[*].test.count[0]

Because module.count[*] matches both the From and To addresses of the parent, the edges would be added in both directions resulting in a cycle.

The graph we actually want in this case looks like

module.count->module.count[0]
module.count[*].test.count->module.count[*].test.count[0]
  module.count->module.count[0]

with a connection only from the inner move to the outer move, which matches the same order of operations when the outer module is changing the name entirely. We achieve this by checking if the dependent move statement is only changing the module index with a new from.MoveModuleReIndex(to) method, and skip adding the graph edge.

Fixes #30208

While not contributing to the cycle, it was noticed in #30208 that impliedMoveStatements was not correctly calling itself recursively, which is also fixed and tested by this PR.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.