chore(deps)!: update to Angular 19

[arturovt]

No description provided.

[just-jeb]

LGMT, one concern, should we merge #1860 into v19 update (as a breaking change)?
We can also merge the current PR as is but keep it in beta until we merge the breaking changes.
@arturovt wdyt?

[arturovt]

We can merge those breaking changes first and I will rebase this branch later.

[mshima]

Hi, thanks to your work.

Unless a new v18 release is planned I think the v19 migration should be merged before.

• those breaking changes seems to be only related to custom-esbuild which have limited usage.
• this PR is much broader than the custom-esbuild only changes.
• this PR is ready and will allow betas or even a final version of packages except esbuild like happened with jest in the past.

[just-jeb]

@arturovt I agree with @mshima, especially taking into account that #1860 may cause breaking changes.

[LanderBeeuwsaert]

It would be nice to get this merged. This is the only package blocking us (and I can imagine that there are other projects in the same situation) from moving to angular 19.

[p1n5u]

Is there any timeline for the release of this update? we are in the same position as @LanderBeeuwsaert and this is the only package that is blocking the migration to angular 19.

[arturovt]

@arturovt I agree with @mshima, especially taking into account that #1860 may cause breaking changes.

Ok, lemme rebase and let it go