EPIC: Drop support for old vectordb SDKs

[wjones127]

We have old vectordb SDKs in Rust and Javascript. We would like to drop support in favor of the newer lancedb SDKs, so we don't have to maintain two different SDKs.

Part 1: Feature parity

What features do we need in newer SDKs to have parity with old ones?

• Feature: allow nodejs API to specify read/write params #1040
• Feature: expose versioning in LanceDB Node / Rust #1007
• bug(node): list of number input causes panic #758
• bug(node): Several bugs when trying to setup a simple use case #882
• Feature: port python's embedding funtions to Rust #994
• Feature(nodejs): Table.search function for lancedb sdk #1256
• bug(node): unable to 'add' to a table created from python #1289
• Feature(nodejs): Table.toArrow function #1254

Part 2: Cleanup

What do we need to do to wrap up the old SDKs

• Delete node directory from codebase.
• Remove mentions of vectordb package from docs. Migrate all examples to lancedb. Feature: update docs to use async APIs #1044

[westonpace]

I had started a somewhat similarly-intentioned list here: #996 However, I think they are slightly different. I added #994 as I think that is the main feature gap between vectordb and lancedb today. Almost all of the examples use embedding functions in some way and so I struggled to switch over the docs and eventually abandoned it for now.