Add ability to parse backend blocks present in a test file's run blocks, validate configuration

[SarahFrench]

Description

Note: This PR is targeted at a feature branch instead of main, as I'd like to avoid creating a single, large PR for this work. My intention is to do a few PRs into that branch and eventually make a PR for the whole feature branch into main. That's when the change file would be included.

This PR is the first step of adding support for backend blocks to run blocks in terraform test:

• implement parsing of backend blocks from run blocks.
• implement validation of backend blocks in the context of runs.

Luckily we can reuse the existing code for parsing backend blocks, so validation is the main problem being addressed in this PR.

Validation requirements

• Only state backends are supported
• Only one backend block per run block
• Only one backend block per internal state file (i.e. state_key value)
  • Update run blocks to have their state key value set earlier if not explicitly set via config; needed to allow proper validation here
• For a given internal state file, the first command = apply run block must be where the backend block is used (if at all)
• Backend blocks must be unique within a given test file

[liamcervante]

I think we're not checking anywhere that only the first run block for a given state can

Edit by Sarah : Need to check that the run with the the backend is the first apply command for that internal state

[SarahFrench]

The crashes resulting from feb5a7b show that we're not setting the state key properly after the changes in 158151c.

I think that's because we don't set ConfigUnderTest until here:

terraform/internal/configs/config_build.go

Line 34 in 3f4ed7e

diags = append(diags, buildTestModules(cfg, walker)...)

and that code runs after we parse individual run blocks etc.

State keys aren't being set in time for validating use of backend blocks yet

[SarahFrench]

The latest changes have:

• Made sure that state keys for child modules are set during parsing of test files
• Removed use of GetStateKey
• Added some more tests that can adapt to runs being processed in different orders

[SarahFrench]

Sorry for the back and forth here! Previously I thought the different ordering that impacted the acceptance test were due to new behaviour in the test graph, but it was just due to iterating over a map 🤦🏻 . I've addressed that in 75dfe43

[dsa0x]

Thanks for addressing that last bit 🫡

[SarahFrench]

Thanks both! 🙇🏻