Blaze: use translated post type name in post-publish panel

[jeherve]

Proposed changes:

Instead of relying on the raw post type slug, let's pull the translated post type label. We need to ensure it is lowercase, since it's used in a sentence.

Before	After

Note
In the French translation above, I had to move the non-translated post type name at the end of the string, where it looked less worse standing on its own. Once this fix is merged and shipped, I will be able to update the translated string again to form a proper sentence without parenthesis.

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

• N/A

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

• No

Testing instructions:

• Go to Settings > General, and switch your site language to French.
• Go to Dashboard > Updates, and update translations if necessary.
• Go to Posts > Add New, write a new post.
• Publish your post.
• View the post-publish panel and its Blaze section; the post type name should be translated.

[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 plugin. Once the plugin is active, go to Jetpack > Jetpack Beta > Jetpack and enable the fix/blaze-post-publish-i18n branch.

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

  bin/jetpack-downloader test jetpack fix/blaze-post-publish-i18n
  

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.
  
• ⚠️ All commits were linted before commit.
  
• ✅ 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.

---

Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team Review" label and ask someone from your team review the code. Once reviewed, it can then be merged.
If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.

[jeherve]

I had to update with latest trunk after merging another PR, so this will need another approval I'm afraid.
Thank you!