Continuous release with pkg.pr.new and esm.sh

[limzykenneth]

Resolves #8570

Changes:

Add dev dependency and workflow required to enable continuous release. Still need to verify that the deployment and custom message is working as intended.

[p5-bot]

Continuous Release

CDN link

• https://raw.esm.sh/pr/p5@a76e0b8/lib/p5.min.js

Published Packages

• https://pkg.pr.new/p5@a76e0b8

Commit hash: da8a336

Previous deployments

da8a336

• https://raw.esm.sh/pr/p5@a76e0b8/lib/p5.min.js
• https://pkg.pr.new/p5@a76e0b8

28ae294

• https://raw.esm.sh/pr/p5@74659d6/lib/p5.min.js
• https://pkg.pr.new/p5@74659d6

---

This is an automated message.

[limzykenneth]

@ksen0 @davepagurek This is done now and ready for review. The build and release are triggered on pull request event so each push update will run it, similar to the regular test CI; it will also run on push to dev-2.0 branch which should mean that there will always be a head commit build.

Once built, the package will be published to pkg.pr.new in the same manner as publishing on NPM except it will be tagged with the specific commit rather than version number. Once publish, esm.sh will automatically pick it up and the relevant CDN link will be available. We should change the CI build run to require approval for all external contributors before merging this.

Also involved is the comment bot @p5-bot, which will comment on PR like the above with relevant links ready to be used. "CDN link" is the link ready to be used in a script tag; "Published Packages" is the link that can be npm installed. As additional push are made to the PR and new version is built and published, the previous link will be recorded in the collapsible section under the relevant commit hash that the build is generated from.

Please review the implementation to check I didn't miss any specific edge cases especially in terms of any unintended publishing. Once it all looks good we can squash and merge since the history here is mostly trial and error stuff from me.