Fixed test failing in different timezones

[mehrabisajad]

Impact

• Enhancement/New feature (adds functionality without impacting existing logic)

• Breaking change (fix or feature that would cause existing functionality to change)

• Bug fix (non-breaking change which fixes expected existing functionality)

Description

The regular expression was edited for time zones with a half-hour offset and a 45-minute offset so that the test could run successfully.
like : UTC−03:30 and UTC+03:30

[github-actions]

Unit Test Results

  4 608 files  ±0    4 608 suites  ±0   32m 58s ⏱️ - 3m 29s
  4 589 tests ±0    4 375 ✔️ ±0     214 💤 ±0  0 ❌ ±0 
54 240 runs  ±0  49 232 ✔️ ±0  5 008 💤 ±0  0 ❌ ±0 

Results for commit dd96535. ± Comparison against base commit bcd2d53.

[nvoxland]

Code review and test results:

Things to be aware of:

• Change to make the test assertion less "assume the minutes are the same" makes sense given the problem
• Only changes a test

Things to worry about:

• Nothing

[XDelphiGrl]

• PR addresses a failing test.
• No additional testing required.

APPROVED

Although the change in this PR could not impact any of the test suites, I'm including links to passing runs for completeness.
Passing Functional Tests
Passing Test Harness Execution