feat(rum-angular)!: support angular ivy

[devcorpio]

Related to #1345

Summary

The changes in this PR will make it possible to use Angular RUM integration in Angular Ivy Applications, including Angular 16.

E2E tests work properly in each of the browsers we support.

Angular 16 app using RUM agent WITHOUT the changes

Angular 16 app using RUM agent WITH the changes

--
The new changes are only compatible with Angular >=12.

Note: From Angular 12 is not possible to disable Ivy

See below the behaviour with older versions:

Angular 9 output:

Angular 10 output

Angular 11 output

How to test

Bear in mind that there are other ways to test this, but this is my favourite way (closer to the reality, users install packages):

1. Checkout the PR's branch
2. Install Verdaccio and start it (make sure you are authenticated)
3. Publish rum agent in Verdaccio
   • Change the registry value from lerna.json file to http://localhost:4873
   • add "angular_ivy_support"in the allowBranch property
   • execute npx lerna publish --no-git-tag-version --no-push
4. You can confirm that everything has been published by going to http//localhost:4873
5. In your angular app install the RUM angular package: npm install @elastic/apm-rum-angular@latest --registry http://localhost:4873

[vigneshshanmugam]

Alberto and myself had a chat offline, we will update the E2E to angular 16 to make it easier for users to reference our example.

[sergey-tihon]

May we expect some alpha npm package any time soon to test Ivy support?

[devcorpio]

Alberto and myself had a chat offline, we will update the E2E to angular 16 to make it easier for users to reference our example.

We had a follow-up, we will not do this, for the reasons:

• Angular > 12 drop support for IE11 (which wasn't particularly a problem, this wasn't the blocker)
• Angular 16 doesn't support Node.js 14 - which is the version we use in the agent, so we needed to upgrade to Node.js 16
• Update to Node.js implies supporting NPM 7, which opens a new can of worms

That's why it was decided to do this in a separated tech debt issue, now it's not the right time to do this update

[devcorpio]

hi @sergey-tihon,

I added a "how to test" section in the PR's description

[vigneshshanmugam]

LGTM 🎉 , Tested with Angular 16 and works as expected.