chore(CI): directory specific test change pruning

[apeabody]

Description

(includes a de minimis sample change to force a test)

Checklist

Readiness

• Yes, merge this PR after it is approved
• No, don't merge this PR after it is approved

Style

• My sample follows the rules described for Terraform in the Effective Samples style guide
• My sample follows the other requirements and best practices in the Contributing
  guide

Testing

• I have performed tests described in the Contributing guide:

  • Tests pass: terraform apply
  • Lint pass: terraform fmt check

Intended location

• Yes, this sample will be (or already is) included on cloud.google.com
  Location(s):

• No, this sample won't be included on cloud.google.com
  Reason:

API enablement

• If the sample needs an API enabled to pass testing, I have added the service to the Test setup file

Review

• If this sample adds a new directory, I have added codeowners to the CODEOWNERS file

[glasnt]

@apeabody did you plan on iterating on this one more? it's been unchanged in drafts for a while

[apeabody]

@apeabody did you plan on iterating on this one more? it's been unchanged in drafts for a while

Hi @glasnt - Yeah, I think this is still valuable, just needs some more time investment to handle a few final edge cases (e.g. intermediate folders contain .tf). I think I can fit it in this quarter.

[glasnt]

Looks like the infra change escape is now working, but we can't easily test the rest of the logic until this code is merged (without shenanigans)

[glasnt]

Approved in theory; cannot be tested without an actual test to validate the logic.