[CT-2462] Grab Bag Task to Track GHA Deprecation Resolution

[emmyoop]

High Level Task

Update workflows to remove deprecation warnings.

Acceptance Criteria

The following repositories have no deprecations. Note that some of the repos have open PRs to fix some or all of the deprecations and just need to be reviewed.

• [CT-2479] replace all instances of set-output and node16 dbt-core#7452
• [ADAP-485] replace all instances of set-output and node16 dbt-snowflake#577
• [ADAP-486] replace all instances of set-output and node16 dbt-spark#740
• [ADAP-487] replace all instances of set-output and node16 dbt-redshift#417
• [ADAP-488] replace all instances of set-output and node16 dbt-bigquery#678
• replace all instances of set-output and node16 dbt-extractor#63
• replace all instances of set-output and node16 dbt-release#77
• [CT-2481] replace all instances of set-output and node16 dbt-rpc#131
• [CT-2482] replace all instances of set-output and node16 homebrew-dbt#288
• replace all instances of set-output and node16 hologram#53
• replace all instances of set-output and node16 tree-sitter-jinja2#15
• [CT-2484] replace all instances of set-output and node16 #93
• replace all instances of set-output and node16 dbt-core-bundles#18
• replace all instances of set-output and node16 dbt-database-adapter-scaffold#55
• replace all instances of set-output and node16 dbt-server#222

These are pending some questions and don't contain any outdated node references

• [CT-2480] replace all instances of set-output and node16 dbt-docs#415

Details

set-output and (save-state but I'm not sure we're using it) will be deprecated 5/31/2023. We need to update actions appropriately. This could be do while also centralizing workflows (#38, #23, etc)

Official Details: GitHub Actions: Deprecating save-state and set-output commands | GitHub Changelog

Also node16 by 9/1/2023

https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/

This will require looking at the workflows and actions we reference. Easiest way is to look at logs from workflow outputs as there will be deprecation warnings.

Known culprits:

1. actions/checkout@v2
2. actions/download-artifact@v2
3. actions/upload-artifact@v2
4. actions/setup-python
5. definitely more

All relevant changes to backport will be tracked in #730

[emmyoop]

sourcegraph is a great tool to find all occurrences of various usages:

Example:
https://sourcegraph.com/search?q=context%3Aglobal+repo%3A%5Egithub%5C.com%2Fdbt-labs+actions%2Fcheckout%40v2&patternType=standard&sm=1&groupBy=repo

Evolving list of what to look fore
actions/checkout@v2
actions/upload-artifact@v2
actions/setup-python@v3

You can also manually check the output from actions for deprecations messages.

[emmyoop]

All these changes are going to need to be backported because we run a lot of actions off *.latest branches.

[davidbloss]

sourcegraph is a great tool to find all occurrences of various usages:

☝️ yes!

Note for anybody that might pick up one of these tickets.
On a per-repo basis I am using rg from the command line to get a condensed view of GH actions as I update them.
rg " uses: " | cut -d ':' -f 3 | sort | uniq