feat(EQP): allow automated submissions to Magento Marketplace upon release in Github.

[damienwebdev]

I'm not a fan of the current submission process for my OS work to the Magento Marketplace.

The Marketplace UI is fairly tedious, subject to the whims of the modern world of UI design as opposed to "concrete" data-driven design, and less than ideal for a streamlined developer process.

For clarity, to make this point more salient, there are also some minor things that are annoyances that such an action would allow me to automate, but these may be outside the scope of such an action.

Such as:

1. standard-version, the tool I use to implement semver, doesn't track a version in composer.json. This means that the composer.json in my source zip is different than the delivered zip, which is tedious to maintain.

2. .gitignore isn't allowed in Marketplace, resulting in failed source bundle submissions.

3. Docs, in theory, could be auto-generated by turning a docs website into a PDF.

It would be lovely if this repo published a Github Action that allowed me to publish updates to my package to the Magento Marketplace automatically as releases are created in Github.

As an MVP, It would be nice to allow for at least only technical updates/technical submissions for an existing package that is assumed to have all the marketing shenanigans already filled out.

To summarize, this would vastly improve my quality of life as an extension developer and would hopefully improve the TTL of critical updates to the marketplace, drastically reducing delays.

[jissereitsma]

This is a great plan. But as there is currently only a Marketplace API but not API client, I would suggest that someone would first work upon creating a client. Such a client is then usable in a GitHub Action like this.