parser: Accept PASSWORD REQUIRE CURRENT DEFAULT (#53306)

[ti-chi-bot]

This is an automated cherry-pick of #53306

What problem does this PR solve?

Issue Number: close #53305

Problem Summary:

1. This only accepts CREATE USER ... PASSWORD REQUIRE CURRENT DEFAULT. It doesn't support PASSWORD REQUIRE CURRENT OPTIONAL.
2. This isn't stored, checked or validated.

What changed and how does it work?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

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

Please refer to Release Notes Language Style Guide to write a quality release note.

TiDB now accepts `PASSWORD REQUIRE CURRENT DEFAULT` as part of `CREATE USER` to aid MySQL 8.0 compatibility

[dveeden]

/retest

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (release-7.5@112a821). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.5     #54559   +/-   ##
================================================
  Coverage               ?   71.9978%           
================================================
  Files                  ?       1412           
  Lines                  ?     410958           
  Branches               ?          0           
================================================
  Hits                   ?     295881           
  Misses                 ?      95181           
  Partials               ?      19896           

Flag	Coverage Δ
unit	71.9978% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9913% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	53.4477% <0.0000%> (?)

[YangKeao]

/retest

[YangKeao]

/retest

[YangKeao]

LGTM

[bb7133]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bb7133, YangKeao
Once this PR has been reviewed and has the lgtm label, please assign bb7133, yudongusa for approval, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS [YangKeao,bb7133]
• pkg/parser/OWNERS [bb7133]

  Need more approvers for rest parts.

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-07-15 08:02:14.799286938 +0000 UTC m=+254556.790228400: ☑️ agreed by YangKeao.
• 2024-07-22 03:24:34.209507489 +0000 UTC m=+842696.200448959: ☑️ agreed by bb7133.

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