Date incorrectly parsed for browsers in UTC+ timezones

[trafton]

Describe the bug

Flight Search needs to work correctly from any time zone

When a user is using a browser in a time zone in Europe and Asia, i.e., UTC-0 through UTC-+12, this component will incorrectly parse the date resulting in it rendering the day before even though the underlying data contains the correct date.

To Reproduce

Steps to reproduce the behavior:

1. Set the time zone of your computer to any positive time zone, e.g., Amsterdam.
2. Go to ascom and search for any flight.
3. When you get to the matrix results page, note that the shoulder dates are one off.
4. If you inspect the auro-pane element, you will see that it had the correct date, but was parsed incorrectly,

Expected behavior

The auro-pane element will show the correct date regardless of the user's time zone.

Screenshots

[blackfalcon]

This issue has been discussed with the Auro team and we are actively looking into a solution and potential release ASAP.

[AuroDesignSystem]

🎉 This issue has been resolved in version 1.1.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀