MERL-1136: Deploy WP Plugin - Github Actions

[matthewguywright]

Description

Updated release-packages workflow in Github to deploy the wordpress plugin.

Testing

Ensure the plugin is deployed during the pipeline running for release. As this only happens during release, we can't test it except locally for the version in the script.

LOCAL:
We had to get the version for the plugin to be deployed. To get the version locally:

1. Pull branch
2. Create a feature branch
3. Create a PR for the branch
4. Watch the version be output by the Test Plugin Version build step
5. There should be a version equal to xx.xx.xx or .x.x.x, ex. "0.8.9"

[changeset-bot]

⚠️ No Changeset found

Latest commit: 45ac68d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

📦 Next.js Bundle Analysis for @faustwp/getting-started-example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[blakewilson]

I see from the output in the test action, that the proper version 0.8.9 was saved to the env var:

https://github.com/wpengine/faustjs/actions/runs/5968538931/job/16192566006?pr=1549

This looks good! There is no real way to test this unless we do a real release, so we'll want to double check it was effective once we do a plugin release.

Before we merge, Let's remove the .github/workflows/test.yml file as well just for tidying up.

[mindctrl]

Just formalizing Blake's suggestion:

Before we merge, Let's remove the .github/workflows/test.yml file as well just for tidying up.