feat: 🎸 add support for v8.2.x, v9.1.x, v10.2.x

[NachoVazquez]

PR Checklist

Please check if your PR fulfills the following requirements:

• [ x ] The commit message follows our guidelines: CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• [ x ] Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ x ] 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?

Missing support for some minor version of Angular

Issue Number: 1

What is the new behavior?

Adds supports for version 8.2.x, 9.1.x, 10.2.x of Angular.

Does this PR introduce a breaking change?

[ ] Yes
[ x ] No

Other information

Solves issues: #1

[LayZeeDK]

How do we bump the version number?

[NachoVazquez]

How do we bump the version number?

yarn release

One important thing to notice is that before a release is ready we have to build the actions and commit the dist files. I know it sounds weird but it is the way it is done because Github uses those files directly from the repo to deploy the action.

yarn build
yarn package

This can be useful

https://github.com/actions/toolkit/blob/master/docs/action-versioning.md
https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/creating-a-javascript-action