feat: use github actions to confirm and upload plugin details to db

[mmackz]

Details

• Introduces a plugin-details.yml file in the template.
• Builder will ask for app and icon url during the setup process for a new plugin. This is optional and these details can be filled in afterwards.
• When the github actions are triggered, they check to see if a new package (plugin) is present, and verifies that it has a valid plugin-details.yml file. If a new package is detected and there is no config, or the config is not valid, the action will fail.
• When the pr is merged to main, an action will run to send the details from the plugin-details.yml to the staging and production api. The details will already be validated at this point.

Backend Changes

---

Issues

• In the scripts, there is some namespace conflicts wherever trying to use a variable that is declared in another script file. I got around this by prefixing any reused variable name with an underscore, but I feel this should not be happening.

• When updating the config file with a new image url, it wont change the image on the S3 bucket unless you use a different name. Image updates do work, the old image is just cached for a while. 😀

---

Testing

I have done a lot of testing locally.

Passes

• when all details are valid in new plugin config file
• when all details are valid on updated config file
• when all details are valid, adding a new config file to existing package
• when making non-config related changes (passes with "no changes found")
• when multiple valid tasks are provided

Fails

• when mandatory details are missing
• when image is too big
• when image url is not an image
• when icon or applink is not a url
• when a new package is detected and no config file is found
• when adding an invalid config file to an existing package
• when updated an existing config file using invalid details

[changeset-bot]

🦋 Changeset detected

Latest commit: cd9c0c9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@rabbitholegg/create-plugin	Minor

Not sure what this means? Click here to learn what changesets are.

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

[mmackz]

Closed the old one since it brought in a bunch of commits from my test branch.

#271

[mmackz]

Fully tested this using multiple scenarios. It is working as intended.