Chore: Use a maintained upload-release-asset

[stumpylog]

Proposed change

The release run had some warnings about Node 12 actions and set-output usage. This transitions us to a new, maintained action which I think should resolve the warnings.

Type of change

• 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)
• Other (please explain) - maintenance

Checklist:

• I have read & agree with the contributing guidelines.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
• If applicable, I have checked that all tests pass, see documentation.
• I have run all pre-commit hooks, see documentation.
• I have made corresponding changes to the documentation as needed.
• I have checked my modifications for any breaking changes.

[shamoon]

Totally defer to you, I guess they archived that one in favor of https://github.com/softprops/action-gh-release but we only need the upload-release-asset part of things?

[stumpylog]

Yeah, the release-drafter action handles creating the release (and the changelog), but it doesn't do the upload. It suggests the now archived action for that.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.