ddl: Fix logging cause by non-dropped table (#8955)

[ti-chi-bot]

This is an automated cherry-pick of #8955

What problem does this PR solve?

Issue Number: close #8911

Problem Summary:

After #8910, if some tables are not able to be dropped, SchemaSyncService::gcImpl will run again with the same gc_safepoint.
But in this path, SchemaSyncService::gcImpl always return true. So if there are some tables can not be dropped for some bugs, then this function will run again and again and print lots of loggings.

What is changed and how it works?

if succeeded == false, then let SchemaSyncService::gcImpl run again after ddl_sync_interval_seconds

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

None

[JaySon-Huang]

/run-all-tests

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JaySon-Huang, JinheLin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [JaySon-Huang,JinheLin]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-04-18 05:49:12.072713509 +0000 UTC m=+489971.183759960: ☑️ agreed by JaySon-Huang.
• 2024-04-18 05:50:40.267379879 +0000 UTC m=+490059.378426325: ☑️ agreed by JinheLin.