@W-12627096@ Translate en-US and en-GB by default

[wjhsf]

Description

With all of the small changes lately, remembering to extract to en-GB is annoying, when the script only does en-US by default. It's a trivial change to fix it, so I fixed it.

Types of Changes

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (could cause existing functionality to not work as expected)
• Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

• Removing a public function or component or prop
• Adding a required argument to a function
• Changing the data type of a function parameter or return value
• Adding a new peer dependency to package.json

Changes

• (change1)

How to Test-Drive This PR

• (step1)

Checklists

General

• Changes are covered by test cases
• CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

• There are no changes to UI

or...

• Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
• Changes comply with WCAG 2.0 guidelines levels A and AA
• Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

• Changes include a UI text update in the Retail React App (which requires translation)

[alexvuong]

Nice! 👍

[bfeister]

@wjhsf is this opt-in? E.g. can a customer opt out of the behavior if it's not desired? I see in the package.json change that we are explicit about <command> en-US en-GB so that implies "yes" to me

[wjhsf]

The customer can specify whatever locales they choose, if that's what you're asking about.

[bfeister]

Assuming it's opt-in (I believe it is from reading the code), LGTM