[Store] Allow id to be int|string|Uuid for VectorDocument and TextDocument

[MolloKhan]

Q	A
Bug fix?	no
New feature?	yes
Docs?	no
Issues	Fix #857
License	MIT

I gave this a second thought, and I think @OskarStark idea is the way to go (#857 (comment))
If the ID coming from the store is in Uuid format the user will likely cast it themself

If you are ok with my changes, I'll proceed to update all the places where VectorDocuments are instantiated

[chr-hertel]

that should also be changed in TextDocument than, right?

[MolloKhan]

I think this is it

[chr-hertel]

One issue we have now is for users not using the Uid component but receiving Uuid instances even if they used string before.

I think the best solution here is to just drop the dependency to the component. no feature of the component itself - besides the type-declaration - actually needs a Uuid and it was a wrong assumption of mine in the beginning based on starting with Pinecone as store 🙈

[MolloKhan]

Good thinking. I'd need only to remove the Uuid auto-casting from the constructor, right?

[MolloKhan]

I removed the Uuid auto-casting and only left the type declaration

[OskarStark]

Can we simplify something in the demo/ folder? Or not needed?

[chr-hertel]

Can we simplify something in the demo/ folder? Or not needed?

wouldn't know what, don't think so.

but i think a valid follow up would be to kill UUID dependency in store component

[chr-hertel]

Can you please rebase this once and have another look at MongoDb, Weaviate, Typesense, Milvus, MariaDb, and Meilisearch?

I think your changes in bridge implementations for removing the Uuid::fromString(...) make sense, but is not done everywhere.

Thanks already @MolloKhan!