Storages: fix adding delta vector index does not work with existing indexes (#9975)

[ti-chi-bot]

This is an automated cherry-pick of #9975

What problem does this PR solve?

Issue Number: close #9971, close #9972

Problem Summary:

What is changed and how it works?

1. Fix the existing index infoes in ColumnFileTiny are missed after add new indexes.
2. Do not add task into `LocalIndexerScheduler` if the DMFile is empty.
3. Fix delta data do not build the new added local indexes.

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

Fix an issue where adding new vector indexes could result in performance regression due to accidental removal of existing vector indexes

[ti-chi-bot]

This cherry pick PR is for a release branch and has not yet been approved by triage owners.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

1. It must be approved by the approvers firstly.
2. AFTER it has been approved by approvers, please wait for the cherry-pick merging approval from triage owners.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

@Lloyd-Pottiger This PR has conflicts, I have hold it.
Please resolve them or ask others to resolve them, then comment /unhold to remove the hold label.

[JaySon-Huang]

/unhold

[JaySon-Huang]

/approve

[ti-chi-bot]

@JaySon-Huang: It seems you want to approve this PR, I will help you trigger all the tests:

/run-all-tests

• Currently the CI jobs are not prow job style, we need it to notify Jenkins server to run them.
• If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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]

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