[BugFix] informationschema.task_runs timezone fix (backport #52123)

[mergify]

Why I'm doing:

informationschema.task_runs timezone fix

What I'm doing:

Fixes #52121

mysql> SELECT TASK_NAME,CREATE_TIME FROM information_schema.task_runs WHERE TASK_NAME = 'mv-54287' ORDER BY CREATE_TIME DESC LIMIT 0,10;
+-----------+---------------------+
| TASK_NAME | CREATE_TIME |
+-----------+---------------------+
| mv-54287 | 2024-10-20 12:27:10 |
+-----------+---------------------+
1 row in set (0.03 sec)

mysql> SELECT TASK_NAME,CREATE_TIME FROM information_schema.task_runs WHERE TASK_NAME = 'mv-54287' AND CREATE_TIME >= '2024-10-19 00:00:00' ORDER BY CREATE_TIME DESC LIMIT 0,10;
+-----------+---------------------+
| TASK_NAME | CREATE_TIME |
+-----------+---------------------+
| mv-54287 | 2024-10-20 12:27:10 |
+-----------+---------------------+
1 row in set (0.04 sec)

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 3.3
  • 3.2
  • 3.1
  • 3.0
  • 2.5

---

This is an automatic backport of pull request #52123 done by [Mergify](https://mergify.com). ## Why I'm doing: informationschema.task_runs timezone fix

What I'm doing:

Fixes #52121

mysql> SELECT TASK_NAME,CREATE_TIME FROM information_schema.task_runs WHERE TASK_NAME = 'mv-54287' ORDER BY CREATE_TIME DESC LIMIT 0,10;
+-----------+---------------------+
| TASK_NAME | CREATE_TIME |
+-----------+---------------------+
| mv-54287 | 2024-10-20 12:27:10 |
+-----------+---------------------+
1 row in set (0.03 sec)

mysql> SELECT TASK_NAME,CREATE_TIME FROM information_schema.task_runs WHERE TASK_NAME = 'mv-54287' AND CREATE_TIME >= '2024-10-19 00:00:00' ORDER BY CREATE_TIME DESC LIMIT 0,10;
+-----------+---------------------+
| TASK_NAME | CREATE_TIME |
+-----------+---------------------+
| mv-54287 | 2024-10-20 12:27:10 |
+-----------+---------------------+
1 row in set (0.04 sec)

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud