Github Actions: "set-output" deprecation

[vielmetti]

Noted in the logs, a complaint from Github about the "set-output" command, as seen in the "Setup SSH

integration-k8s-packet/.github/workflows/ci.yaml

Lines 86 to 96 in 368a83d

	- name: Setup ssh
	working-directory: ${{ github.repository }}
	id: setup_ssh
	run: |
	ssh-keygen -t rsa -f /tmp/sshkey -q -N ""
	eval `ssh-agent -s`
	ssh-add /tmp/sshkey
	ssh_id=$(metal ssh-key create --key "$(cat /tmp/sshkey.pub)" --label ${SSH_KEY} -o json | jq -r '.id')
	echo ::set-output name=ssh_id::${ssh_id}
	env:
	METAL_AUTH_TOKEN: ${{ secrets.PACKET_AUTH_TOKEN }}

The feature is being deprecated, per

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

and the suggested fix is something like this:

A workflow using save-state or set-output like the following

- name: Save state
  run: echo "::save-state name={name}::{value}"

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

should be updated to write to the new GITHUB_STATE and GITHUB_OUTPUT environment files:

- name: Save state
  run: echo "{name}={value}" >> $GITHUB_STATE

- name: Set output
  run: echo "{name}={value}" >> $GITHUB_OUTPUT

[vielmetti]

There is a little time to fix this:

We are monitoring telemetry for the usage of these commands and plan to fully disable them on 31st May 2023. Starting 1st June 2023 workflows using save-state or set-output commands via stdout will fail with an error.

[denis-tingaikin]

@vielmetti Many thanks for the report. Should be resolved for the packet testing by #315

[denis-tingaikin]

Seems like its still actual, because some of repos were updated incorrectly.

@wazsone Could you please re-do this?