fix(angular): button components now routes correctly without reload

[liamdebeasi]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally and any changes were pushed
• Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

Issue URL: #25014 (comment)

#25014 caused all routerLinks to perform a page reload which interfered with the local history of Ionic's routing integrations. This resulted in ion-back-button elements disappear because Ionic thought users could not go back.

This change was originally done to allow a elements to open links in new tabs via Ctrl+Click.

What is the new behavior?

• Reverts the change in fix(angular): routerLink allows opening in a new tab for link elements #25014
• Excludes a elements from Ionic's routerLink delegate so that Ctrl+Click works correctly.

Does this introduce a breaking change?

• Yes
• No

Other information

[sean-perkins]

Angular does have a router link implementation that targets specifically the a and area tags: https://github.com/angular/angular/blob/master/packages/router/src/directives/router_link.ts#L280-L281

Should we do a similar approach? Have the previous implementation pattern target a and have the updated implementation target the selector within this PR?

I believe with this change clicking the a tag without a new tab interaction, will not apply the element specific overrides for router direction & animation.