Issue 29209 - Enforce order store locale in sales email address / order creation display

[zaximus84]

Description (*)

When an order is placed on the store front and sales emails are triggered from the admin, the locale of the order's store is not properly applied to the country (in billing or shipping address) or the formatted order creation date.

Example: Frontend store view is French and admin is in English. Order is placed using a US address. Original order email will say "États-Unis" for country and "28 janv. 2021 18:14:06" for order date. However, resending the order email from the admin says "United States" and "Jan 28, 2021, 6:14:06 PM".

This PR properly applies the locale of the order's store to order address country and formatted creation date.

Fixed Issues (if relevant)

1. Fixes getFormattedShippingAddress / getFormattedBillingAddress #29209

Manual testing scenarios (*)

1. Have the admin locale set to English.
2. Create a store view with locale set to French.
3. Create an order from the French store view with United States as the shipping / billing address country.
4. Confirm that the new order email has a French formatted date / time (Ex: 28 janv. 2021 18:14:06) and country is "États-Unis".
5. Log into admin, view the order, and click Send Email.
6. Confirm that the email matches the original and does NOT say "United States" or have a US-formatted date (Jan 28, 2021, 6:14:06 PM)

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @zaximus84. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel