Move cuvs-lucene to cuVS

[cjnolet]

When we first began exploring a cuVS plugin for lucene, it made practice sense to keep it as a separate repository.

But now that the plugin has matured, it's not proving to make much sense to have it as its own separate repository- for example, we need to deploy docs and it would be much easier for everyone (users and maintainers) to have the docs become part of cuVS itself.

Also, since cuVS is already a hard requirement of cuVS-lucene, this will make the ci much more straightforward to maintain.

[cjnolet]

Adding justification from #172 cuVS-lucene was originally a separate repository while NVIDIA needed to give special access to external contributors, but now that the code and packages are well established, we need to roll this into cuVS. First benefit is that the docs can be consolidated so that we don't need to maintain two completely separate sets of docs. Second benefit is that we can track everything in 1 place, and manage 1 single CI. Third benefit is that the cuvs-java and cuvs-lucene code can better be managed together- we don't need to rely on packages being deployed for cuvs-java or on rebuilding cuvs-java inside cuvs-lucene, and we can further rely on the libcuvs packages from the cuvs CI directly.

Activity