[ENH] Consume HNSW from config

[itaismith]

Description of changes

• Consume HNSW parameters from a collection's HNSWConfiguration instead of metadata.
• Remove usage of hnsw: metadata values to set HNSW parameters.
• Migrate older versions to use the new HNSWConfiguration.

Test plan

• property tests to validate new behavior with various HNSWConfigurations.
• cross_version to test migrating to new behavior.

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

WIP

• Add documentation to demonstrate how to set HNSW parameters with an HNSWConfiguration.

Note: API work on configuration builders is also in progress.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)