ttl: fix ttl job manager will panic if the status cache doesn't contain table (#41069)

[ti-chi-bot]

This is an automated cherry-pick of #41069

Signed-off-by: YangKeao [email protected]

What problem does this PR solve?

Issue Number: close #41067, close #41068

Problem Summary:

1. The log of scan error doesn't contain error information.
2. Job manager will panic if the status cache doesn't contain table.

What is changed and how it works?

1. Replace the err with sqlErr
2. Pass in the jobID directly. We could start this job anyway, as the job manager actually did little things, and can be processed by other managers in the future. Also, the tasks has been spawned, we'd better to keep the task locally.

I cannot reproduce the second situation in a natural way (except deleting the rows with concrete breakpoint). I'll add some tests about it after I understand how it occurs...

Could we try to restart the ttl job manager after it panics?

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• hawkingrei
• lcwangchao

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[YangKeao]

It also picks some parts of #41069, to resolve the conflict.

[hawkingrei]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: f0a55a1

[ti-chi-bot]

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

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

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/test-infra repository.