Get rid of deprecated set-output commands in GitHub Actions

[roryabraham]

Problem

GitHub deprecated the set-output command in workflows, and they will "soon be disabled".

https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
https://github.com/Expensify/App/actions/runs/3252739822/jobs/5339300870

Why is this important?

These were deprecated for security reasons, and if we don't update our workflows then they will stop working soon.

Solution

Update to using the new environment files.

[roryabraham]

Got a PR up for most of our usages of set-output, but not necessarily all the usages in the community actions we're using.

[melvin-bot]

@roryabraham Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[roryabraham]

Reopening to continue migrating community actions.

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist will need to be completed before the issue can be closed:

• A regression test has been added or updated so that the same bug will not reach production again. Link to the updated test here:
• The PR that introduced the bug has been identified. Link to the PR:
• The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• A discussion in #contributor-plus has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• Payment has been made to the issue reporter (if applicable)
• Payment has been made to the contributor that fixed the issue (if applicable)
• Payment has been made to the contributor+ that helped on the issue (if applicable)

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist will need to be completed before the issue can be closed:

• A regression test has been added or updated so that the same bug will not reach production again. Link to the updated test here:
• The PR that introduced the bug has been identified. Link to the PR:
• The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• A discussion in #contributor-plus has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• Payment has been made to the issue reporter (if applicable)
• Payment has been made to the contributor that fixed the issue (if applicable)
• Payment has been made to the contributor+ that helped on the issue (if applicable)

[roryabraham]

The Bug0 checklist is safe to ignore here I think. Was just doing a migration forced by GitHub

[melvin-bot]

Triggered auto assignment to @miljakljajic (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[miljakljajic]

What action should I take here, sorry?

[roryabraham]

This is not a bug, going to remove you and the bug label

[roryabraham]

tspascoal/get-user-teams-membership is an outdated action I need to migrate. Probably will just replace it with the GH cli

[roryabraham]

Anyone can continue working on this, but I'm not going to prioritize it right now. Adding it to the tracking issue and dropping it for now.

[fukawi2]

Looks like this has all been done now:

phs ~/Expensidev [main !?] $ grep -RH ::set-output */.github
phs ~/Expensidev [main !?] $

[fukawi2]

Reassigning to @roryabraham since he did most of the work by the look of it, so credit due.