Use Link instead of ExternalLink

[tbradsha]

Proposed changes

The new @wordpress/use-recommended-components ESLint rule nudges people to use the Link component from @wordpress/ui instead of the ExternalLink component from @wordpress/components.

It should be a drop-in replacement with a openInNewTab prop. Styles are intended to be on par (WordPress/gutenberg#77790).

This was mostly straightforward, but a few additional tweaks were required to make CI happy:

• Translations don't play friendly with the default Webpack configs, so I had to enable BundledWpPkgsTranspileRules() in several projects.
• There were two local component name conflicts I adjusted: 25d05ee and 3493131
• ai-chat was trying to bundle react as a dependency, so I switched that to a normal <a>: 41a1b2f
• There was a Text → Link → Text → span wrapper making linters unhappy, so I removed the inner Text and changed the outer Text to use its variant: f54678e
• The above required a snapshot update: ec26b3d

Related product discussion/links

Does this pull request change what data or activity we track or use?

Testing instructions

Along with smoke testing, I'd suggest reviewing code by commit in the following order:

1. Normal changes: bd50c86
2. Docs, tests, and createInterpolateElement(): 6f9fc0b
3. Go through the "additional tweaks" listed earlier.

[jp-launch-control]

Code Coverage Summary

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/plugins/jetpack/modules/subscriptions/newsletter-widget/src/components/dashboard-link.tsx	10/10 (100.00%)	0.00%	0 💚

Full summary · PHP report · JS report

[simison]

Yep 👍 This will mostly just need cursory smoke testing since the components are so similar.

I have a bit deeper-going PR to swap usage in Forms: #48407

[CGastrell]

There is disparity with the styles, but it's acceptable. Checked some places to use as sample, didn't test them all. Code looks good

[CGastrell]

LGTM!