[FLINK-38424][planner] Support to parse VECTOR_SEARCH function

[fsk119]

What is the purpose of the change

Support to parse VECTOR_SEARCH function.

Brief change log

• Add SqlVectorSearchTableFunction
• Add type inference for the newly added function
• Set the correct scope for VECTOR_SEARCH function

Verifying this change

This change added tests and can be verified as follows:

• Added plan tests for VECTOR_SEARCH function

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (yes / no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
• The serializers: (yes / no / don't know)
• The runtime per-record code paths (performance sensitive): (yes / no / don't know)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
• The S3 file system connector: (yes / no / don't know)

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

[flinkbot]

CI report:

• 6209929 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[davidradl]

nit: search -> searches

[davidradl]

It would be interesting to compare it to a LookupTableSource also.

[davidradl]

I an see what TOP_K is from googling. It would be useful to add in the documentation describing the parameters with this change - including the default. I wonder if we should add paging, to be able to handle a large number of results or is this not done with vector databases.