Node 12 warnings

[niemyjski]

Using this action is causing some warnings to be outputted:

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: kolpav/purge-artifacts-action
--
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

[kolpav]

The first line of readme or the linked issue in it might clarify why:) on serious note using github-script to achieve similar results might be the way to go and this might be the reason reason why there is no 0 day retention policy or something like that.

[p0358]

The thing is, retention policy would not achieve what people using such actions want imo.

What a lot of people want is to purge old artifacts when a new one is being created, but otherwise keep them as long as can be retained, so that other workflows can still use them (in other words, to only store the artifacts from latest workflow run)

Perhaps it's only a coincidence that your repo was perfectly solving this use-case, when all you wanted to do was to remove all artifacts after artifact run, but it was working perfectly fine for our use-case