feat(supported-version): add all kind

[damienwebdev]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/graycoreio/github-actions-magento2/blob/main/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

I wasn't confident that the code I have in place for #35 actually supports every version out there.

Fixes: N/A

What is the new behavior?

As such, I've added a new kind to trial against ALL Magento versions.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[ihor-sviziev]

Just one question - why do we need the supported-version/dist/index.js file?

[damienwebdev]

@ihor-sviziev I prefer writing in typescript, and Github's recommendation is to build to js and commit. see: https://github.com/actions/typescript-action

[ihor-sviziev]

Sorry, my question was about supported-version/src/kind/all.json

[damienwebdev]

@ihor-sviziev that was a miss on my part.

[damienwebdev]

The underlying bugs here are results of issues between the @mage-os mirror and upstream Magento.

The mirror is building from tags in the repo, whereas mainline Magento has packages tagged as one version, but published as another.

The offending package appears to be the Adobe Stock Integration. See: magento/adobe-stock-integration#1872

See also: magento/adobe-stock-integration#1873

corrected.