executor: adapt to the go1.21 map loadFactor setting value (#50545)

[ti-chi-bot]

This is an automated cherry-pick of #50545

What problem does this PR solve?

Issue Number: close #50544 and #50552

Problem Summary:

What changed and how does it work?

This PR is trivial.
As the discussion indicates load factor of map in 1.21 would be 6 rather than 6.5 in other version. The whole test of TestaggPartiualResultMap depends on the assumption that load factor of map in golang would be 6.5.
To adopt this breaking behavior, the codebase of tidb should makes changes accordingly.

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

[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.

[ti-chi-bot]

@ti-chi-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/check_dev_2	b6fe086	link	true	/test check-dev2
idc-jenkins-ci-tidb/unit-test	b6fe086	link	true	/test unit-test
idc-jenkins-ci-tidb/build	b6fe086	link	true	/test build
idc-jenkins-ci-tidb/mysql-test	b6fe086	link	true	/test mysql-test
idc-jenkins-ci-tidb/check_dev	b6fe086	link	true	/test check-dev

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[zhexuany]

@XuHuaiyu could you please approve this cherry-pick?

[zhexuany]

/cherry-pick-invite

[ti-chi-bot]

@zhexuany you're not a member of org pingcap

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid

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 [AilinKid]

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-01-21 15:28:56.900566764 +0000 UTC m=+715378.464864454: ☑️ agreed by AilinKid.

[zhexuany]

@AilinKid Does not have the privilege to modify changes in tichibot's repo.

Is it possible close this cherry-pick request and approve the change in this CP #50581.