[DOC] Add enterprise packaging, ABI stability, and implications to docs

Vendors and users who ultimately want to benefit from our new build and enterprise support strategy ultimately need to make some considerations when integrating cuVS- for example, rather than building and packaging cuvs directly, they'll need to use our upcoming tarball packaging and assume their users will be installing cuvs separately. They'll also need to use our C APIs or any of the API wrappers built on top of it, rather than using C++ direclty.

The reasoning behind these implications is not immediately obvious for most users, so we should add a section to our docs explaining why these are important, their implications, the plans and guarantees, etc... so that we can point users to a consistent and cohesive (public) messaging.

No documentation file or test is named in the issue, so first locate the existing public documentation and the current packaging and ABI guidance. The work is done when a cohesive section explains the rationale, implications, plans, and guarantees for tarball packaging and using the C APIs or their wrappers.