[v8] Merge angular & angular-ivy packages

[mydea]

Currently, we publish @sentry/angular which targets older angular versions, and @sentry/angular-ivy which targets newer versions.

In v8, we want to go back to only publishing a single @sentry/angular package which is basically the current @sentry/angular-ivy. angular-ivy will no longer be published.

The new @sentry/angular package will support Angular 13+

Open questions

• Should we support Angular 13+ or have an even higher limit?

Related issues

closes #9448
closes #10511

[mydea]

@Lms24 can you evaluate which versions we actually want to support, when you find some time :)

[Lms24]

Yup, will do!

[jdussouillez]

Should we support Angular 13+ or have an even higher limit?

From the official Angular documentation:

Angular versions v2 to v14 are no longer supported.

And v15 LTS support ends in 2 months (2024-05-18). I don't know when you want to release v8 but if it's not before 2 months, I would say supporting v16+ is enough.

[Lms24]

Hey @jdussouillez I'm aware of Angular's support policy, it's just that our own support policy/philosophy is a little bit stricter. IOW we want to support old versions for as long as possible in general because we don't want to "force" users to update their framework just because of us. And let's face it, older Angular versions are still used quite extensively.

As to Angular, admittedly, our philosophy poses a lot of problems and I am actually contemplating jumping to NG15. Even if I get NG17 working with an NG14 compatible SDK, Angular can't guarantee compatibility with NG18 when it's out 😭

I didn't investigate the exact lower bound version enough yet because we're still working on more foundational tasks for v8. But soon I'll take a serious look and update everyone following this issue.