planner: fix create binding panic when status.record-db-qp enable (#29519)

[ti-srebot]

cherry-pick #29519 to release-5.0
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/30372

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tidb.git pr/30372:release-5.0-7feb0e667b5f

---

What problem does this PR solve?

Issue Number: close #29503

Problem Summary:

1. We forget to check the nil for ast.SelectStmt.From. When we create the empty table query, it will cause panic. E.g, select 1.
2. We forget to assign tableInfo and dbInfo to ast.StmtNode when we create the binding and the config record-db-qps enable.
3. We forget to check the nil in getStmtDbLabel function for *ast.CreateBindingStmt, it will cause panic when the table is empty.

What is changed and how it works?

1. Check the nil for ast.SelectStmt.From.
2. Assign tableInfo and dbInfo to ast.StmtNode when we create the binding and the config record-db-qps enable.
3. Check the nil in getStmtDbLabel function for *ast.CreateBindingStmt.

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

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

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.

[ti-chi-bot]

@ti-srebot: 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.

[ti-srebot]

/run-all-tests

[ti-srebot]

@Reminiscent you're already a collaborator in bot's repo.

[Reminiscent]

The changes to the PR depend on other PRs that do not have Cherry-pick. If the changes are too large, the risk is uncontrollable, so consider not cherry-pick first. If there is a need in the future, we will reopen the PR.