go.mod: upgrade gin version from v1.8.1 to v1.9.1

[niubell]

What problem does this PR solve?

Issue Number: Close #7438

What is changed and how does it work?

Upgrade Gin version to v1.9.1 to solve some security issues

Check List

Tests

• Integration test
• Manual test (add detailed scripts or steps below)

Code changes

Side effects

Related changes

• Need to cherry-pick to the release branch

Release note

Upgrade Gin version to v1.9.1 to solve some security issues.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• HuSharp
• rleungx

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 submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-chi-bot]

Hi @niubell. Thanks for your PR.

I'm waiting for a tikv member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[rleungx]

/ok-to-test

[codecov]

Codecov Report

Merging #7451 (cf75fc7) into master (a09717b) will decrease coverage by 0.10%.
Report is 1 commits behind head on master.
The diff coverage is n/a.

❗ Current head cf75fc7 differs from pull request most recent head 0f5fba5. Consider uploading reports for the commit 0f5fba5 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7451      +/-   ##
==========================================
- Coverage   74.25%   74.15%   -0.10%     
==========================================
  Files         451      451              
  Lines       49692    49593      -99     
==========================================
- Hits        36898    36775     -123     
- Misses       9488     9517      +29     
+ Partials     3306     3301       -5     

Flag	Coverage Δ
unittests	74.15% <ø> (-0.10%)	⬇️

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

[rleungx]

How about merging line 66-73 with line 75?

[niubell]

done

[JmPotato]

/merge

[ti-chi-bot]

@JmPotato: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and 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.

If you have any questions about the PR merge process, please refer to pr process.

Details

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.

[ti-chi-bot]

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

Details

Commit hash: 0f5fba5

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #7459.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #7514.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #7515.