feat: Add utility methods to simplify InMemoryVectorStore creation

[cvauclair]

• Add InMemoryVectorStore::from_documents utility method
• Add InMemoryVectorStore::from_embeddings utility method
• Add docstrings
• Update example

Previously:

let model = openai_client.embedding_model("text-embedding-ada-002");

let mut vector_store = InMemoryVectorStore::default();

let embeddings = EmbeddingsBuilder::new(model.clone())
    .simple_document("doc0", "Definition of a *flurbo*: A flurbo is a green alien that lives on cold planets")
    .simple_document("doc1", "Definition of a *glarb-glarb*: A glarb-glarb is a ancient tool used by the ancestors of the inhabitants of planet Jiro to farm the land.")
    .simple_document("doc2", "Definition of a *linglingdong*: A term used by inhabitants of the far side of the moon to describe humans.")
    .build()
    .await?;

vector_store.add_documents(embeddings).await?;

let index = vector_store.index(model);

Can now be written as:

let model = openai_client.embedding_model("text-embedding-ada-002");

let embeddings = EmbeddingsBuilder::new(model.clone())
    .simple_document("doc0", "Definition of a *flurbo*: A flurbo is a green alien that lives on cold planets")
    .simple_document("doc1", "Definition of a *glarb-glarb*: A glarb-glarb is a ancient tool used by the ancestors of the inhabitants of planet Jiro to farm the land.")
    .simple_document("doc2", "Definition of a *linglingdong*: A term used by inhabitants of the far side of the moon to describe humans.")
    .build()
    .await?;

let index = InMemoryVectorIndex::from_embeddings(model, embeddings).await?;

Or even shorter if using InMemoryVectorIndex::from_documents!

[0xMochan]

Looks good. I also see there's an opportunity for fluid builder design on the openai_client.embedding_model(...) that could make it a bit cleaner but understandably makes the requirements on other provider clients a bit hazy.

[cvauclair]

Looks good. I also see there's an opportunity for fluid builder design on the openai_client.embedding_model(...) that could make it a bit cleaner but understandably makes the requirements on other provider clients a bit hazy.

I think we might end up with traits for Clients to simplify this integration, but that will be tackled in another issue!