Add test for `useLocalizeDate`

Feature Request

Description

While we are adding the useLocalizeDate hook, we found out we didn't test getLocaleString function at all.

But when we try to add the test, we are hitting timezone problem. Timezone of the CI box and local box could be different.

To mitigate the problem, we need to add some code in production codebase to allow the user to select timezone. For example, the options passed to Intl.DateTimeFormat should have { timeZone: 'utc' }.

Instead of doing it in the PR, we are adding a new issue and address it later.

Actual code

import { timeouts } from '../constants.json';

// selenium-webdriver API doc:
// https://seleniumhq.github.io/selenium/docs/api/javascript/module/selenium-webdriver/index_exports_WebDriver.html

jest.setTimeout(timeouts.test);

test('calling localizeDate should return a localized date time string', async () => {
  const { pageObjects } = await setupWebDriver();

  await expect(
    pageObjects.runHook('useLocalizeDate', [new Date(2000, 0, 2, 12, 34, 56)])
  ).resolves.toMatchInlineSnapshot(`"January 02, 20:34"`);
});

[Enhancement]

Start from the useLocalizeDate hook and its getLocaleString function, then inspect the Jest test using setupWebDriver and the inline snapshot. Make the date formatting and test independent of the machine timezone while allowing the intended timezone option, and verify the localized output with the test.