executor, codec: hash join build wrong hash key for ENUM value

[winoros]

This is a manual cherry-pick for #49031

What problem does this PR solve?

Issue Number: close #48991

Problem Summary:

What changed and how does it work?

When the projection disables the ColumnEvaluator, it will eval the ENUM and parse a new ENUM. But the new ENUM value's value index will be set to 0.

But when we construct the hash value for the join key, we use the value index to seek the string value. So a wrong hash key is constructed.

This pull aims to solve the case.

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.

Fix the issue that hash join will construct wrong join key for ENUM type

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (release-6.5@e5ee37e). Click here to learn what that means.
The diff coverage is n/a.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-6.5     #49032   +/-   ##
================================================
  Coverage               ?   73.6447%           
================================================
  Files                  ?       1087           
  Lines                  ?     349433           
  Branches               ?          0           
================================================
  Hits                   ?     257339           
  Misses                 ?      75579           
  Partials               ?      16515           

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: guo-shaoge, XuHuaiyu

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 [XuHuaiyu,guo-shaoge]

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:

• 2023-11-30 07:40:04.491973763 +0000 UTC m=+1081233.157199958: ☑️ agreed by XuHuaiyu.
• 2023-11-30 08:01:52.585985998 +0000 UTC m=+1082541.251212193: ☑️ agreed by guo-shaoge.