Add link to reader profile on /me page

[artemiomorales]

Related to #99015
Additional context here: p1738106541068789-slack-C083J8DHLLD

Proposed Changes

Adds a link and description to the reader profile on the /me page.

Why are these changes being made?

We'd like to provide an easily accessible link to users so they can see their reader user profiles.

Testing Instructions

• Go to the /me page
• Ensure the new link exists
• Ensure the correct username is being used
• Make sure the link works as expected

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-131578

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-131578&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-131578&env=a8c-for-agencies

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• notifications

To test WordPress.com changes, run install-plugin.sh $pluginSlug add/profile-link-on-me-page on your sandbox.

[matticbot]

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

Sections (~196 bytes added 📈 [gzipped])

name                   parsed_size           gzip_size
site-blocks                 +790 B  (+0.1%)     +196 B  (+0.1%)
security                    +790 B  (+0.1%)     +196 B  (+0.1%)
purchases                   +790 B  (+0.0%)     +196 B  (+0.0%)
privacy                     +790 B  (+0.1%)     +196 B  (+0.1%)
notification-settings       +790 B  (+0.1%)     +196 B  (+0.1%)
me                          +790 B  (+0.1%)     +196 B  (+0.1%)
help                        +790 B  (+0.1%)     +196 B  (+0.1%)
developer                   +790 B  (+0.1%)     +196 B  (+0.1%)
account-close               +790 B  (+0.1%)     +196 B  (+0.1%)
account                     +790 B  (+0.1%)     +196 B  (+0.1%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

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.

[Addison-Stavlo]

Just a small comment below wrt the link staying in the same environment, but this looks good and works for me.

[Addison-Stavlo]

I think using the https://wordpress.com bit in the visible URL makes sense for the users perception. But for the anchor href i might simply go with /read/users/${username}, that way if we are doing a walkthrough or testing on a testing environment like horizon, calypso.live, or localhost, the link moves us to the profile but keeps us in the same environment (instead of pushing us back to production).

[artemiomorales]

Good point! That's been updated.

[davemart-in]

Looks and works great. Nicely done.

[mehmoodak]

Suggested change

	const relativeProfileUrl = `/read/users/${ this.props.user.username }`;
	const relativeProfileUrl = getUserProfileUrl( this.props.user.username );