Refactor release flow and use `changeset` to manage versioning

[TuvalSimha]

• [x] Add changeset @TuvalSimha
• [x] Add renovate-bot to the repo @kamilkisiela
• [x] Add NPM_TOKEN secret @kamilkisiela
• [x] Set publishConfig if needed @TuvalSimha
• [x] Remove old release scripts @TuvalSimha
• [x] Test on PR (using changeset file) @TuvalSimha
• [ ] Test stable release (from master) @TuvalSimha
• [x] Add to CONTRIBUTING.md explaining about changeset, how to use it, etc...

[github-actions[bot]]

### 🚀 Website Preview The latest changes to the website are available as preview in: [https://6b6eaeb6.apollo-angular.pages.dev](https://6b6eaeb6.apollo-angular.pages.dev)

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 36e5c7ce38de3fee451f0939e8b513fe7bdcc39b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[github-actions[bot]]

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):	Package	Version	Info
apollo-angular	4.2.1-alpha-20230125113210-0fc1de1c	npm ↗︎ unpkg ↗︎

[dotansimha]

Thanks @PowerKiKi ! @TuvalSimha I think we are good to go 🚀 (you need a rebase and then you should be able to merge)