chore: Setup workflow for plugin BETA releases

[colinmurphy]

Overview

When merging into main for a modified plugin (currently webhooks or previews), we should be creating a release for this plugin.

The naming convention should be currently prefixed with "beta-[GITHUB SHA]" so users can identify the release as BETA.

[colinmurphy]

Workflow for Releasing a Plugin

Pre-requisites

1. Setup changeset bot in the repository like we have on Faust and Content Blocks
   • https://github.com/apps/changeset-bot
2. Any plugin that wants to use this should have a package.json (thanks Joe) and a CHANGELOG.md file.

High level workflow

1. PR creation for a plugin

1. A PR is created with changes to the plugin
2. Changeset bot checks for changeset for a plugin (can be configured. See Faust.js https://github.com/wpengine/faustjs/blob/canary/.changeset/config.json)
3. A changeset is added.
4. The plugin follows our normal PR review process (defined in https://github.com/wpengine/hwptoolkit/blob/main/HOW_WE_WORK.md)
5. And then the PR is merged into the main branch.

2. Changeset bot workflow

1. This should then create a PR for the changeset (e.g. on Faust - Version Packages faustjs#2112)

2. This should contain the following:

   • Release notes for the plugin and updated the CHANGELOG.md file
   • Deleted the changeset file
   • Updated the version for the plugin

3. Once merged it should then trigger the release workflow

3. Release workflow

See Faust.js as an example -https://github.com/wpengine/faustjs/blob/canary/.github/workflows/release-packages.yml

1. Check if there was a changeset to the plugin
2. If so then run the release workflow action:
   • Creates a zip using composer archive
   • Uploads this as part of a GH release
   • The release should be called "hwp-previews-vX.Y.Z" where X.Y.Z is the version of the plugin

[colinmurphy]

PR for changsets to add the changset bot - #272