parser: update to go1.19

[hawkingrei]

What problem does this PR solve?

Issue Number: close #50765

Problem Summary:

What changed and how does it work?

go1.22 has been released. so we update parser to go1.19.

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.

None

[codecov]

Codecov Report

Merging #51032 (bd32721) into master (7d27a9a) will increase coverage by 2.0714%.
Report is 2 commits behind head on master.
The diff coverage is n/a.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #51032        +/-   ##
================================================
+ Coverage   70.5358%   72.6072%   +2.0713%     
================================================
  Files          1467       1467                
  Lines        434895     436240      +1345     
================================================
+ Hits         306757     316742      +9985     
+ Misses       108848      99533      -9315     
- Partials      19290      19965       +675     

Flag	Coverage Δ
integration	49.2588% <ø> (?)
unit	70.3101% <ø> (-0.0263%)	⬇️

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

Components	Coverage Δ
dumpling	54.1120% <ø> (ø)
parser	∅ <ø> (∅)
br	51.2594% <ø> (+5.5096%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, lance6716

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [D3Hunter,lance6716]
• pkg/parser/OWNERS [D3Hunter]

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-02-07 04:55:44.559102323 +0000 UTC m=+332670.125872214: ☑️ agreed by lance6716.
• 2024-02-07 05:33:31.050429705 +0000 UTC m=+334936.617199596: ☑️ agreed by D3Hunter.