[WIP]Presto Lance Connector

[beinan]

Description

Motivation and Context

Impact

Test Plan

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

General Changes
* Add LanceDB connector :pr:`22749`

[steveburnett]

Suggest add PR number to the release note entry, as follows:

== RELEASE NOTES ==

General Changes
* Add LanceDB connector :pr:`22749`

[tdcmeehan]

This might be orthogonal, but does it also make sense to add integration into the Lance file format? I am just thinking of ML pipeline observability/debugging.

[beinan]

This might be orthogonal, but does it also make sense to add integration into the Lance file format? I am just thinking of ML pipeline observability/debugging.

Good point! I'm thinking integrating Lance's format with Prestissimo could be more natural, considering Lance already provides an arrow-based interface.
This PR might be more focus on metadata and query planning part

[steveburnett]

Understanding this is currently WIP, will documentation be added for this new connector?

[tdcmeehan]

@beinan how will the metadata work? Does it integrate with an existing catalog like HMS, or does it require a custom catalog?