terraform test: Try applying orchestratord version

[def-]

Seen failing in https://buildkite.com/materialize/nightly/builds/13598#01998374-9277-42a0-bd72-1673bb5a94e6

Follow-up to #33701

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

[def-]

@alex-hunt-materialize I need some help here, test is still failing the same way.

[def-]

@bobbyiliev Maybe you have an idea here? My best guess is that terraform is somehow not setting the orchestratord version correctly?

[bobbyiliev]

@def- I figured out the initial issue and got the orchestrator working here: #33748

The problem is with the way Terraform does the yaml merge :/ So a quick fix here is to just explicitly specify all attributes.

However, now the environmentd pod is not starting, so I'm looking into that.

[def-]

The problem is with the way Terraform does the yaml merge :/ So a quick fix here is to just explicitly specify all attributes.

This has been an issue with GCP/AWS too, one of the reasons the other terraform tests are currently disabled.

[def-]

Bobby fixed this up better: #33748