Makefile: add a lint for parser's keywords

[HuSharp]

What problem does this PR solve?

#54246 has not updated keywords, maybe we need a lint to check parser/keywords

Issue Number: Ref #54245

Problem Summary:

What changed and how does it work?

When meet error

$ make parser_genkeywords
make[1]: Entering directory '/data/nvme0n1/husharp/proj/tidb/pkg/parser'
go generate
make[1]: Leaving directory '/data/nvme0n1/husharp/proj/tidb/pkg/parser'
--- keywords.go.committed       2024-07-23 14:35:57.829246693 +0800
+++ keywords.go 2024-07-23 14:36:00.505309768 +0800
@@ -622,6 +622,7 @@
        {"VALIDATION", false, "unreserved"},
        {"VALUE", false, "unreserved"},
        {"VARIABLES", false, "unreserved"},
+       {"VECTOR", false, "unreserved"},
        {"VIEW", false, "unreserved"},
        {"VISIBLE", false, "unreserved"},
        {"WAIT", false, "unreserved"},
make: *** [Makefile:147: parser_genkeyword] Error 1

After fixing error

master* $ make parser_genkeywords
make[1]: Entering directory '/data/nvme0n1/husharp/proj/tidb/pkg/parser'
go generate
make[1]: Leaving directory '/data/nvme0n1/husharp/proj/tidb/pkg/parser'

Check List

Tests

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

  • I checked and no code files have been changed.

Release note

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

None

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign d3hunter for approval. 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
• pkg/parser/OWNERS

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

[tiprow]

Hi @HuSharp. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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-sigs/prow repository.

[HuSharp]

@breezewish @tangenta @glorv PTAL, thx!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.7438%. Comparing base (cdd7c9e) to head (f7c8a80).

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #54827        +/-   ##
================================================
- Coverage   72.7769%   72.7438%   -0.0332%     
================================================
  Files          1557       1557                
  Lines        437912     437912                
================================================
- Hits         318699     318554       -145     
- Misses        99582      99663        +81     
- Partials      19631      19695        +64     

Flag	Coverage Δ
unit	71.7502% <ø> (-0.0404%)	⬇️

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

Components	Coverage Δ
dumpling	52.9656% <ø> (ø)
parser	∅ <ø> (∅)
br	45.8002% <ø> (-0.0736%)	⬇️

[breezewish]

Duplicate with #54371?

[HuSharp]

Duplicate with #54371?

Let's close this pr.