Align the VectorSet API with other clients

[tishun]

Feature Request

We need to go over the API for Vector Sets and align it with the implementation in other clients.

Is your feature request related to a problem? Please describe

The first (experimental) implementation was provided to give the early adopters a chance to use the API.
It - however - has some splinters to cut here and there, and needs to be consideredin the light of all the existing implementations:

• Support Redis 8 vector sets #4169 jedis#4203
• Propose vector-set API StackExchange/StackExchange.Redis#2939
• Vector sets node-redis#2998
• Adding VectorSet commands support. redis-py#3584
• feat: support vectorset go-redis#3375
• feat(commands): Add support for VectorSet commands predis/predis#1550

Describe the solution you'd like

We need to:

• align the API, especially with Jedis
• address the issue caught by @mgravell in Feedback: VLINKS return information is incomplete / incorrect docs#1972
• promote the API to final version by removing the @Experimental tags

Describe alternatives you've considered

N/A

Teachability, Documentation, Adoption, Migration Strategy

N/A