updated Intl.DateTimeFormat.prototype.resolvedOptions() tests to reflect recent normative change

[ben-allen]

Address #3812
Fix #3876

tc39/ecma402#758 changes the hourCycle logic in Intl.DateTimeFormat.InitializeDateAndTime() to no longer erroneously assume that h24 is the 24 hour clock expected in locales using h11 or h12 as defaults.

7353744 and 15792da update hourCycle-default.js to reflect the new behaviour.

note: I don't believe any engine currently passes all of the tests in the new hourCycle-default.js. v8 and node fail because they associate h12 with h24, as was required by the old algorithm, while jsc and spidermonkey fail because they ignore the -u-hc-h24 extension when hour12 is set to false, as below:

// sm and jsc
new Intl.DateTimeFormat('en-u-hc-h24', {hour: "numeric", hour12: false}).resolvedOptions().hourCycle;
=> "h23"

commit 2648144 updates hourCycle-dateStyle.js with explanatory comments. Essentially, all this test does is verify that hour12 and hourCycle are set to undefined when dateStyle but not timeStyle is set, but the comments and metadata in the previous version appear to say something different.

[Ms2ger]

Ready when the spec is.

[ptomato]

The normative change reached consensus in the TC39 meeting of 2023-09. Given Ms2ger's approval I think we can merge this. I squashed the updates from addressing code review comments into the original topical commits.