added lancedb contrib

[zilto]

The contrib allows to interact with lancedb by specifying a schema and facilitating read / writes.

For new dataflows:

Do you have the following?

• Added a new folder for my dataflow under my username directory.
  • Added a README.md file under my dataflow directory that follows the standard headings and is filled out.
  • Added a init.py file under my dataflow directory that contains the Hamilton code.
  • Added a requirements.txt under my dataflow directory that contains the required packages outside of Hamilton.
  • Added tags.json under my dataflow directory to curate my dataflow.
  • Added valid_configs.jsonl under my dataflow directory to specify the valid configurations.
  • Added a dag.png that shows one possible configuration of my dataflow.

For existing dataflows -- what has changed?

How I tested this

Tested functions using the included run.ipynb notebook

Notes

Functions are annotated with @tag(side_effect="True") to indicate the interaction with the database.

Checklist

• PR has an informative and human-readable title (this will be pulled into the release notes)
• Changes are limited to a single goal (no scope creep)
• Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Dataflow documentation has been updated if adding/changing functionality.

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: All new business logic should have corresponding unit tests.
• Apply: Refactor large functions to be more modular.

[skrawcz]

@zilto oops -- merged too soon -- we should annotate data with dict, list[dict], pd.DataFrame, or a Iterator[pa.RecordBatch]