lightning,dumpling: make tidb version check more compitible

[glorv]

What problem does this PR solve?

TiDB version string can be customized by set the corresponding config field. So parse the result from select verson() to get tidb release version is not correct in some case.

What is changed and how it works?

• Try to exec select version() and parse the result as tidb version; If the query returns error, fallback to select version(); so we can still be compitible with MySQL/MariaDB.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
  • Run dumpling and lightning(local backend) with TiDB playground v5.2.2 (server-version = 'Test-5.7.22'), both can detect tidb version correctly and export/import successfully
  • Run dumpling and lightning (tidb backend) with MySQL 5.7.22, both can export/import successfully.
• 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

Avoid version check failure when tidb version is customized.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• 3pointer
• lichunzhu

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.

[3pointer]

🤔

[lichunzhu]

Suggested change

	{version.ServerTypeUnknown, consistencyTypeFlush, true},
	{version.ServerTypeMySQL, consistencyTypeFlush, true},

[glorv]

/hold

[glorv]

/unhold

[3pointer]

LGTM

[glorv]

/merge

[ti-chi-bot]

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

Commit hash: 363e05a

[glorv]

/merge

[ti-chi-bot]

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

Commit hash: 5f91996

[glorv]

/run-check_dev

[glorv]

/merge

[ti-chi-bot]

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

Commit hash: 4219e51

[glorv]

/merge

[ti-chi-bot]

@glorv: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

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.

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.