.Net MEVD: Consider removing copy constructor on VectorStoreRecordProperty

[roji]

VectorStoreRecordDataProperty, VectorStoreRecordKeyProperty and VectorStoreRecordVectorProperty have copy constructors, which accept another instance of the same type to copy details from. However, since these types are all immutable (init-initializable only), it's hard to see what would be the use for these.

/cc @westey-m

[westey-m]

The idea was to allow anyone to make copies and just change one property instead of having to copy all. E.g. someone wants the same schema for three DBs, but each supports different distance functions. Everything else stays the same though.

var original = new VectorStoreRecordVectorProperty("DefinitionEmbedding", typeof(ReadOnlyMemory<float>)) { Dimensions = 1536, DistanceFunction = DistanceFunction.DotProductSimilarity };
var copy = new VectorStoreRecordVectorProperty(original) { DistanceFunction = DistanceFunction.CosineDistance };

[roji]

@westey-m thanks, I see... .NET doesn't usually do copy constructors much, and given that there simply aren't many things there, these may not actually be needed (plus they can always be added later). But I don't have very strong feelings on this.