Reader: Use wpcom_login instead of login when linking to user profile

[DustyReagan]

Related to #98868
Requires diff: 171081-ghe-Automattic/wpcom

Proposed Changes

• This PR uses wpcom_login when linking to the user profile page instead of login.

Why are these changes being made?

• login data is inconsistent between Jetpack and wpcom sites. wpcom_login is always the wordpress.com login.

Testing Instructions

• Apply 171081-ghe-Automattic/wpcom to your sandbox and sandbox the API.
• Use Calypso Live and observe the author user name on Jetpack sites (and other sites) links correctly to the user profile page.
• For example the author "demo" on these pages should link to the user profile "dreagan": https://wordpress.com/read/feeds/166062205 and https://wordpress.com/read/feeds/166062205/posts/5534312285

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-131058

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-131058&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 update/read-use-wpcom_login on your sandbox.

[matticbot]

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

Sections (~0 bytes added 📈 [gzipped])

name                             parsed_size           gzip_size
write-flow                             +24 B  (+0.0%)       +0 B
reader                                 +24 B  (+0.0%)       +0 B
plugins                                +24 B  (+0.0%)       +0 B
link-in-bio-tld-flow                   +24 B  (+0.0%)       +0 B
jetpack-cloud-plugin-management        +24 B  (+0.0%)       +0 B
home                                   +24 B  (+0.0%)       +0 B
build-flow                             +24 B  (+0.0%)       +0 B
a8c-for-agencies-plugins               +24 B  (+0.0%)       +0 B

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

Async-loaded Components (~0 bytes added 📈 [gzipped])

name                                                 parsed_size           gzip_size
async-load-design-blocks                                   +24 B  (+0.0%)       +0 B
async-load-calypso-components-web-preview-component        +24 B  (+0.0%)       +0 B

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

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.

[artemiomorales]

Looks good and tests well for me 👍