chore(workflows): use GITHUB_OUTPUT instead of ::set-output

[PixnBits]

https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Description

replace

echo "::set-output name={name}::{value}"

with

echo "{name}={value}" >> $GITHUB_OUTPUT

Motivation and Context

https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
these are now showing as warnings in the runs, e.g. https://github.com/americanexpress/one-app/actions/runs/6344142425

How Has This Been Tested?

americanexpress/one-app#1141

Types of Changes

• Bug fix (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)
• Documentation (adding or updating documentation)
• Dependency update

Checklist:

• My change requires a change to the documentation and I have updated the documentation accordingly.
• My changes are in sync with the code style of this project.
• There aren't any other open Pull Requests for the same issue/update.
• These changes should be applied to a maintenance branch.
• This change requires cross browser checks.
• This change impacts caching for client browsers.
• I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using parrot?

None

[github-actions]

Thank you for your contribution to this repository. We will be reviewing your PR. In the meantime, please sign the CLA and make sure all status checks have passed.