Converts domain names to logmein links

[aneeshd16]

Changes proposed in this Pull Request

This change converts domains to logmein links on domain contact verification page

Testing instructions

• Update the WHOIS details on an ICANN-regulated TLD (gTLDs like com, blog, etc.) and set new first, last or email fields. This should trigger the verification email.
• The link in the email goes through public-api first so you might need to edit it to get to the real link, you can also use this JS snippet:

(new URL(<URL in email>)).searchParams.get('redirect_to').replace('https://wordpress.com','http://calypso.localhost:3000')

• You should see that the domains have been converted to logmein links (with ?logmein=1 appended)
  
• Reload the page, this will show the "already verified" screen which also contains the logmein link for the domain.

Fixes #54548

[a8ci18n]

🆗 This change will be queued for retranslation. We'll use the existing translations in the meantime.

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

App Entrypoints (~64 bytes added 📈 [gzipped])

name                   parsed_size           gzip_size
entry-domains-landing       +147 B  (+0.0%)      +64 B  (+0.0%)

Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[lsl]

LGTM

[a8ci18n]

This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/6245766

Thank you @aneeshd16 for including a screenshot in the description! This is really helpful for our translators.

[niranjan-uma-shankar]

@aneeshd16 A note that we needn't wait for translations because the string modifications here only change the arguments in the string, and there are no copy changes. So, the same translations can be used. You can see in the following link that the "new" strings are marked fuzzy and show the previous translations. If you can verify that the same translations will hold good here, you could "Approve" the strings in the Details section.

https://translate.wordpress.com/projects/wpcom/-all-translated/686035/

[a8ci18n]

Translation for this Pull Request has now been finished.