Admin bar: replace 'Edit Profile' and 'My Account' with 'My Profile'

[fushar]

Related to:

• Reduce jumps between Calypso <> wp-admin when editing profile wp-calypso#95055

Calypso counterpart:

• Masterbar: replace 'Edit Profile' and 'My Account' with 'My Profile' wp-calypso#95062

Proposed changes:

This PR modifies the following submenus in the Howdy, {display menu} menu in the admin bar:

• Point the Edit Profile submenu to /me always (and rename it to My Profile to match the Calypso page name).
• Remove the My Account submenu.

Before	After

The reason is that the profile.php wp-admin page that the Edit Profile currently points to, contains mostly links back to Calypso. The most useful fields (display names, language, email) can only be done at user level in Calypso. So, to reduce jumps between Calypso <> wp-admin interface, this PR proposes that the submenu should point to Calypso.

We'll address how to direct user to the profile.php page from /me (e.g. to update the color scheme) in a later PR.

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

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

Testing instructions:

1. Patch this PR to Simple / Atomic.
2. Go to any wp-admin screen.
3. Click the Howdy menu; verify it points to /me.
4. Click the Howdy -> My Profile submenu; verify it points to /me.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the edit-profile-link branch.

  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin edit-profile-link
  

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• 🔴 Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!