[Meta-issue] Intl operations returning incompatible results on Windows: investigate whether causes are strictly External

The cause or partial cause of many of these issues may be WinGlob. Waiting on completion of #2919 (implement Intl with ICU) to get a better handle on the symptoms and causes.

Determine whether issues are intrinsic to the external library (WinGlob) or whether can be fixed (legitimately or by workaround) in ChakraCore directly.

See related linked-back issues below (also, I closed these issues to keep issue tracker tidy).

* DateTime
* [ ] #599 Intl: new Date().toLocaleString('de') puts unicode (BiDi) markers around punctuation
* [ ] #1408 Intl.DateTimeFormat incorrect formatting of date
* [ ] #3096 Intl: Date.toLocaleString doesn't handle 'timeZoneName' option correctly
* [ ] #3579 Intl: Date.toLocaleString on date/year with >10000 returns an error "Invalid procedure call or argument"
* Time
* [ ] #1223 Intl.DateTimeFormat doesn't format minutes and seconds properly in IE 11 and Edge
* [ ] #2915 Intl: Poor format template choice when specifying hour12 and minute with DateTimeFormatter
* [ ] #2916 Incorrect time reported by Date#toLocaleString
* Currency:
* [ ] #2778 Intl.NumberFormat currency symbols are inaccurate when dealing with different types of dollars/$
* NumberFormat:
* [ ] #3595 Intl: Number.tolocalestring output difference among platforms.
* [ ] #3691 Intl NumberFormat bug for floating point number rounding behavior
* Collation:
* [ ] #2604 "Intl.Collator('generic') fails" (i.e. locale "generic" not supported)
* [ ] #3175 Intl: Tibetan / Dzongkha collation not working
* [ ] #4060 "localeCompare doesn't take into account minus signs" (Collation behavior is different between WinGlob and ICU)