Update dependencies, resolve external-facing deprecations

[GaryGSC]

This was a quick stab at resolving 2.5yrs of tech debt.

This is technically a breaking change due to requiring a newer version of the GitHub runner that can handle using: 'node16', but otherwise it should be a very safe update. At BYU, with the exceptions of an on-prem runner or two and the mobile app team needing Macs, we use runs-on: 'ubuntu-latest'. The breaking change should be a non-issue.

[github-actions]

Terraform Plan in different dir:

will create 2 resources:

• local_file - fake_file
• random_pet - name

see details

[github-actions]

Terraform Plan without wrapper:

will create 2 resources:

• local_file - fake_file
• random_pet - name

see details

[github-actions]

Terraform Plan from root:

will create 2 resources:

• local_file - fake_file
• random_pet - name

see details

[github-actions]

Terraform Plan:

will create 2 resources:

• local_file - fake_file
• random_pet - name

see details

[stuft2]

Except for the linting errors, LGTM.

[GaryGSC]

The lint warnings are odd because they're complaining that I'm passing in an object with a run_id property to a dependency (to pick an example). @stuft2 - Any suggestions on how to fix that?

Maybe if I were to update ESLint and a bunch of the dev dependencies, we'd get different lint errors. It just looked like a royal pain to update those due to all the config files and peer dependencies.

[stuft2]

Unfortunately, I think the only way to get around this is to disable the rule. You could disable it globally but I prefer to disable it per line unless the effort outweighs the benefit.

const example = {
// eslint-disable-next-line @typescript-eslint/naming-convention
  run_id: '<id>'
}

[GaryGSC]

I agree about the per-line/global thing. I'll go ahead and make those changes here.