comment-syntax: Correct the note about --comments (#5421)

[ti-srebot]

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

# In docs repo:
git pr https://github.com/pingcap/docs/pull/5427

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

git push git@github.com:ti-srebot/docs.git pr/5427:release-4.0-ed9ed5b895ff

---

What is changed, added or deleted? (Required)

With the 8.0.23 MySQL client TiDB specific comments are cleared out, so
even with the latest client you still need to add --comments.

Which TiDB version(s) do your changes apply to? (Required)

• master (the latest development version)
• v5.0 (TiDB 5.0 versions)
• v4.0 (TiDB 4.0 versions)
• v3.1 (TiDB 3.1 versions)
• v3.0 (TiDB 3.0 versions)
• v2.1 (TiDB 2.1 versions)

What is the related PR or file link(s)?

• Other reference link(s): SHOW CREATE TABLE output with AUTO_RANDOM results in missing AUTO_RANDOM tidb#24176 (comment)

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[ti-srebot]

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

[TomShawn]

/lgtm

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• TomShawn

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.

Details

Reviewer can indicate their review by writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[TomShawn]

/merge

[ti-chi-bot]

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

Details

Commit hash: fc50624