feat(core): Synchronize changes from internal JSAction codebase.

[iteriani]

1: Remove USE_EVENT_PATH, which has no users.

2: Create a new EventActionInfo object to represent actions, update all EventInfoWrapper users.

3: Fix stopPropagation behavior in JSAction Dispatcher - it should only stopPropagation if an action is found, which is only known during normal dispatch rather than global.

4: Update the internal EventInfo representation of an ActionInfo to match the external representation in EventInfoWrapper.

PR Checklist

Please check if your PR fulfills the following requirements:

• [X ] The commit message follows our guidelines: https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit
• [X ] Tests for the changes have been added (for bug fixes / features)
• [X ] Docs have been added / updated (for bug fixes / features)

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
• angular.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• [X ] No

Other information

[tbondwilkinson]

How many licks does it take to get to the center of a tootsie pop.

#3

[tbondwilkinson]

reviewed-for: primitives-event-dispatch

[mturco]

reviewed-for: primitives-event-dispatch

[AndrewKushnir]

Reviewed-for: primitives

[AndrewKushnir]

@mturco could you please leave a review with the "Reviewed-for: primitives-shared" comment? That should complete the set of required LGTMs for this PR.

[mturco]

Reviewed-for: primitives-shared

[thePunderWoman]

Caretaker note: This isn't in use yet in G3. So we can merge this without a TGP.

[pkozlowski-opensource]

This PR was merged into the repository by commit 1ee9f32.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}