THEMES-1654: Card List block not respecting time format

[vgalatro]

Description

This PR fixes a bug where the card list block would always use the default time format.

Jira Ticket

• THEMES-1654

Acceptance Criteria

The card list block uses the site's time format when it is set

Test Steps

1. Checkout this branch git checkout THEMES-1654
2. In your local blocks.json change the dateTimeFormat property to something noticeably different than the default (such as using %b instead of %B so the short month name appears, or adding %A to show the day of the week).
3. Run fusion repo with linked blocks npx fusion start -f -l @wpmedia/card-list-block
4. Add a Card list - Arc block to a page with a query of type: story and showing a few items.
5. The top most item should show the date and time in the format specified in the blocks.json.

Author Checklist

• Confirmed all the test steps a reviewer will follow above are working.
• Confirmed there are no linter errors. Please run npm run lint to check for errors. Often, npm run lint:fix will fix those errors and warnings.
• Ran this code locally and checked that there are not any unintended side effects. For example, that a CSS selector is scoped only to a particular block.
• Confirmed this PR has reasonable code coverage. You can run npm run test:coverage to see your progress.
  • Confirmed this PR has unit test files
  • Ran npm run test, made sure all tests are passing
  • If the amount of work to write unit tests for this change are excessive,
    please explain why (so that we can fix it whenever it gets refactored).
• Confirmed relevant documentation has been updated/added.

Reviewer Checklist

The reviewer of the PR should copy-paste this template into the review comments on review.

• Linting code actions have passed.
• Ran the code locally based on the test instructions.
  • I don’t think this is needed to be tested locally. For example, a padding style change (storybook?) or a logic change (write a test).
• I am a member of the engine theme team so that I can approve and merge this. If you're not on the team, you won't have access to approve and merge this pr.
• Looked to see that the new or changed code has code coverage, specifically. We want the global code coverage to keep on going up with targeted testing.