For i18n data purposes, map the "bs" locale to "hr" instead of "bs-Cyrl"

[annierm18]

Check existing issues

• I have checked for existing issues to avoid duplicates

Description

Per Babak's comment here, the Bosnian distributor has asked Esri products to use "hr" locale as the substitute for "bs" locale insead of "bs-Cyrl" for i18n data purposes.

Closed issues related to this:
#9387
#4583

Acceptance Criteria

For i18n purposes (not t9n), the "bs" locale should map the the "hr" locale.

Relevant Info

Here is the fix from the JSAPI team - it's issue num 70886. The fix was applied for datetime and numbers.

Which Component

Any components that are impacted by Chromium's lack of support of the "bs" locale. This would include components that use intl, like input-date-picker.

Example Use Case

No response

Priority impact

impact - p2 - want for an upcoming milestone

Calcite package

• @esri/calcite-components
• @esri/calcite-components-react
• @esri/calcite-design-tokens
• @esri/calcite-ui-icons
• @esri/eslint-plugin-calcite-components

Esri team

N/A

[anveshmekala]

@annierm18 In a recent update 71749, js-api is using sr-Latn-CS for bs instead of hr . Wanted to get your thoughts on the preferred fallback value up until Chrome support for bs is available.

[anveshmekala]

And for month to be latn, I don't think we have the nls bundle for hr with latin month abbreviation.

[annierm18]

@anveshmekala I will get back to you on this soon