feat: support Angular Components

[LayZeeDK]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• The latest artifacts are committed (run yarn build)

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?

1. The Angular Components packages are not managed.
2. Outdated packages are not deleted, managed packages are not added.
3. Managed packages are not listed in the readme.

Issue Number: N/A

What is the new behavior?

1. The following packages are now managed:
   • @angular/cdk
   • @angular/google-maps
   • @angular/material
   • @angular/youtube-player
2. Outdated packages are not deleted, managed packages are not added.
3. Managed packages are listed in the readme.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

New behavior introduced because it will start adding more dependencies and delete outdated dependencies. However, this shouldn't affect the consumers. We haven't described how packages are added or removed. It should just magically work as far as the consumer is concerned.

Other information

Version sync strategy for Angular Components packages are documented in CONTRIBUTING.md.

[NachoVazquez]

Looking good, I left some doubts in the comments.

[NachoVazquez]

I'll approve, but I left a suggestion for removing the as any conversion in case you think it makes sense.