Social: Connections API schema front end changes

[manzoorwanijk]

Related to #40677

Proposed changes:

• Use the updated connections schema on the front-end following Move wpcom/v2/publicize/connections endpoint to publicize package #40607

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:

• Go to connections management
• Verify that the connection name is displayed correctly for all the connections
• Remove the display name from your Bluesky profile and reconnect it
• Verify that the display name for the connection is the blueksy handle
• Add a Mastodon connection and then break the connection by removing Jetpack here.
• Change the tab in the edior and come back or reload the page in case of settings page to have the broken connection reflected
• In the editor, verify that the broken connection notice shows up fine.
• Reconnect the broken Mastodon account
• Verify that reconnection works fine (with the correct handle)
• In editor, toggle the connections ON/OFF to confirm it works fine
• Try to send post only to 1 network, rest toggled off to verify it works
• If you have an unsupported network like Twitter added, verify it's marked as unsupported. I verified it for my old Twitter connection.
• In the Jetpack sidebar, click on Preview social posts
• Verify that the connections are displayed fine

[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 update/social-schema-front-end-changes branch.

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

  bin/jetpack-downloader test jetpack update/social-schema-front-end-changes
  

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 a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ 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!

[gmjuhasz]

This looks good to me, but @pablinos should take a look as well as it's a fairly big change