[DNM] *: Support Vector Data Type and Functions

[breezewish]

What problem does this PR solve?

Issue Number: ref #54245

Problem Summary:

What changed and how does it work?

This is the feature branch PR for adding vector data type into TiDB, consists of several independently-reviewed commits.

Vector index is not introduced in this PR.

Because downstream tools do not support vector data type yet, the Vector data type must be explicitly enabled via a GLOBAL variable. This allows other tools to work with this data type and provide compatibilities.

Related:

• Merge TiKV support first: copr: Support Vector Data Type and Functions tikv/tikv#17303

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.

*: Support Vector Data Type

[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 ailinkid, tangenta, xuhuaiyu for approval, ensuring that each of them provides their approval before proceeding. 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/ddl/OWNERS
• pkg/expression/OWNERS
• pkg/parser/OWNERS
• pkg/planner/OWNERS
• pkg/table/OWNERS

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.6942%. Comparing base (1acb8f7) to head (35d053a).
Report is 227 commits behind head on master.

❗ Current head 35d053a differs from pull request most recent head c4a1f18

Please upload reports for the commit c4a1f18 to get more accurate results.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #54901         +/-   ##
=================================================
- Coverage   72.8511%   55.6942%   -17.1570%     
=================================================
  Files          1558       1680        +122     
  Lines        438406     610512     +172106     
=================================================
+ Hits         319384     340020      +20636     
- Misses        99322     247074     +147752     
- Partials      19700      23418       +3718     

Flag	Coverage Δ
integration	23.1741% <ø> (?)
unit	71.7961% <ø> (-0.0622%)	⬇️

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

Components	Coverage Δ
dumpling	52.9656% <ø> (ø)
parser	∅ <ø> (∅)
br	52.5905% <ø> (+6.7162%)	⬆️

[tiprow]

@breezewish: 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
fast_test_tiprow	c4a1f18	link	true	/test fast_test_tiprow
tidb_parser_test	c4a1f18	link	true	/test tidb_parser_test

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

[ti-chi-bot]

@breezewish: 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/unit-test	c4a1f18	link	true	/test unit-test
pull-mysql-client-test	c4a1f18	link	true	/test pull-mysql-client-test
idc-jenkins-ci-tidb/mysql-test	c4a1f18	link	true	/test mysql-test
idc-jenkins-ci-tidb/check_dev	c4a1f18	link	true	/test check-dev
pull-integration-ddl-test	c4a1f18	link	true	/test pull-integration-ddl-test
pull-br-integration-test	c4a1f18	link	true	/test pull-br-integration-test
idc-jenkins-ci-tidb/check_dev_2	c4a1f18	link	true	/test check-dev2
idc-jenkins-ci-tidb/build	c4a1f18	link	true	/test build

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.

[breezewish]

Close for #55550