[BugFix] fix cache select task property not set correctly (backport #45592)

[mergify]

Why I'm doing:

What I'm doing:

mysql> select * from information_schema.tasks;
+-----------+---------------------+-----------------------------------------------------+-----------------+----------+---------------------------------------------------------+-------------+--------------------+
| TASK_NAME | CREATE_TIME         | SCHEDULE                                            | CATALOG         | DATABASE | DEFINITION                                              | EXPIRE_TIME | PROPERTIES         |
+-----------+---------------------+-----------------------------------------------------+-----------------+----------+---------------------------------------------------------+-------------+--------------------+
| aaa       | 2024-05-14 16:16:33 | PERIODICAL START(2024-05-14T16:10) EVERY(1 MINUTES) | default_catalog | test     | cache select * from test.t PROPERTIES("verbose"="true") | NULL        | ('verbose'='true') |
+-----------+---------------------+-----------------------------------------------------+-----------------+----------+---------------------------------------------------------+-------------+--------------------+
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 #45592 done by [Mergify](https://mergify.com). ## Why I'm doing:

What I'm doing:

mysql> select * from information_schema.tasks;
+-----------+---------------------+-----------------------------------------------------+-----------------+----------+---------------------------------------------------------+-------------+--------------------+
| TASK_NAME | CREATE_TIME         | SCHEDULE                                            | CATALOG         | DATABASE | DEFINITION                                              | EXPIRE_TIME | PROPERTIES         |
+-----------+---------------------+-----------------------------------------------------+-----------------+----------+---------------------------------------------------------+-------------+--------------------+
| aaa       | 2024-05-14 16:16:33 | PERIODICAL START(2024-05-14T16:10) EVERY(1 MINUTES) | default_catalog | test     | cache select * from test.t PROPERTIES("verbose"="true") | NULL        | ('verbose'='true') |
+-----------+---------------------+-----------------------------------------------------+-----------------+----------+---------------------------------------------------------+-------------+--------------------+
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