Add fix for trusted advisor metadata coming in unexpected order

[bjfish25]

Proposed changes

It was possible for there to only be 2 metadata fields which was spitting out null-resource errors. This PR fixes this issue by more dynamically checking for the region.

Issues for these changes

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (changes to code, which do not change application behavior)

Checklist

• I have filled out this PR template
• I have read the CONTRIBUTING doc
• I have added automated tests that prove my fix is effective or that my feature works
• I have added necessary documentation (README.md, CHANGELOG.md, etc. - if appropriate)

Dependencies and Blockers

Relevant Links

Further comments

[github-actions]

Unit Test Results

    2 files  ±0      2 suites  ±0   10s ⏱️ ±0s
255 tests ±0  255 ✔️ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit e4e07f3. ± Comparison against base commit 8bad266.