Remove Vector Set Preview Checklist

@metajack is already working on this.

Since Jun 23, 2026.

Now that V1 is no longer receiving Vector Set updates, we can starting working through all the things we need to do to get rid of the `--enable-vector-set-preview` flag.

Link PRs that accomplish tasks to this issue.

In no particular order:
- [x] Recovery (and resumption of interrupted) quantization tables and vectors (#1926 ; though still needs additional testing)
- [ ] Additional testing for ^
- [ ] Logging FFI additions (#1992)
- [ ] Implement `continue_search` for too-big-for-initial-buffers searches (#1992)
- [ ] Tests that `VADD` can _update_ vectors correctly (#2032)
- [x] Remove limit on # of Vector Sets (see #1900)
- [x] `RENAME(NX)` support (see #1913)
- [x] Tests that all commands either `WRONGTYPE` on Vector Sets, or work as expected (#1935)
* Subset here is that _overwriting_ a Vector Set cleans up the Vector Set as expected
- [ ] Tests that migrated Vector Sets retain expiration metadata
- [ ] `VADD` updates need to be correctly ordered in the AOF and replayed in correct order on replicas (#2032)
- [x] RESP3 support for `VSIM` (see #1916)
- [x] `RAW` support for `VEMB` (see #1916)
- [x] `VCARD` (#1935)
- [x] `VISMEMBER` (#1935)
- [ ] `VLINKS` (#1992)
- [ ] `VRANDMEMBER` (#1992)
- [x] `VSETATTR` (#2001)
- [ ] Match (or exceed) Redis limits in filter compilation for compatibility
- [x] Exclude internal vectors data from `KEYS`, `SCAN`, etc. (#1921 ; see #1922)

---

[`VRANGE`](https://redis.io/docs/latest/commands/vrange/) support has been removed from the checklist. `VRANGE` is a weird command that has a number of footguns for the large Vector Sets we expect to see, in particular `-` and `+` options could result in gigabytes of response data. Given that there's no trivial implementation path _and_ the command is of limited utility, we'll wait until there's concrete demand to implement it.