feat: upgrade react-intl lib

[soygitana]

IMPORTANT:

• Minimal set of changes to solve the problem.

Changes:

1. react-intl lib has been upgrade to v6.4.2
2. BUIE has been updated to v^20.0.0

---

Testing:

Make sure application and strings are not broken when language is changed.

---

For more information, please check:

• official upgrade guide
• upgrade process review guide in collaborative spreadsheet

[soygitana]

e549c20:

I have to add resolution for react-intl to package.json file ( "/react-intl//@types/react": "^17.0.2"). react-intl has set @types/react to version 16 || 17 || 18 (https://github.com/formatjs/formatjs/blob/main/package.json#L61) so yarn install the latest one, however @types/react 17 i 18 are incompatible. It caused a mismatch of types in some components.

[soygitana]

4ceb40a:

I removed redundant intlShape from mock.

[soygitana]

Regarding @box/frontend package:

@box/frontend is currently set to "^6.4.0," while the latest version is 9. However, similar to the Preview repository, this repo doesn't utilize language bundles. Therefore, there's no need to upgrade it in response to the react-intl update. I'll maintain @box/frontend at version 6, and you can update it later if necessary.

[ehoogerbeets]

Approved from an i18n point of view. Still needs product team's approval as well.

[jstoffan]

Do we need this exact version or can we prefix with a caret?

[soygitana]

I am not 100% sure. Normally, we should use a caret. However, I discovered that react-intl version 6.4 specifies TypeScript version 4 in peerDependencies, while react-intl 6.5 requires TypeScript version 5. I am concerned that this might cause some issues, that is why I used exact version. I think they should update the react-intl package version to 7 when making this change, but they haven't done so.

[jstoffan]

Got it, thank you for the explanation. Should we bump to 6.4.7, in that case?

[jstoffan]

@soygitana, this is good to merge as-is if we don't want to mess with the patch version bump right now.

[soygitana]

❗ On hold: BUIE should go first, then Preview and Annotations (confirmed by @greg-in-a-box)