Add Intl API Support for Hermes JS Engine

[dedavis6797]

Summary

The goal for this issue is to bring Hermes to parity with its predecessor Intl implementations, ensuring alignment with the ECMA-402 specification.

Motivation

Hermes currently lacks support for Intl APIs that were available in its predecessor, Chakra/V8. This gap causes issues for customers requiring i18n integration for features like date, time and string formatting based on client device locale settings. Related discussions on this topic can be referenced in items facebook/hermes#630 and (MSFT INTERNAL) Deliverable 36976172.

Tasks

Preview Give feedback

1. Adds in Intl.getCanonicalLocales #117
   +0
2. Adds in default Intl.DateTimeFormat #127
   +0
3. Add DateTimeFormat::formatToParts #132
   enhancement +1
4. Add order to DateTimeFormat::resolvedOptions #141
   bug +1
5. Add Intl::Collator #134
   enhancement +1
6. Add Intl::NumberFormat #135
   enhancement +1
7. Add Intl toLocaleLowerCase and toLocaleUpperCase #136
   enhancement +1
8. Support Intl bestFit matching #137
   enhancement +1

Current Status

There's a PR of a basic datetimeformat object with documented limitations. Due to the amount of time and effort it takes to add these objects, we will do them on an as-needed basis.

[mganandraj]

Removing the "Needs triage" tag as the work is already in progress.