proposal: Publish the RPC client package and align versions with Neovim

[alsi-lawr]

Publish the RPC client package as the primary NuGet package, rather than publishing the remote-plugin host package.

Motivation

The RPC client is the reusable library surface consumers need for communicating with Neovim. The remote-plugin host is legacy-adjacent and has a separate removal/simplification path in #26. Publishing should focus on the RPC client package and align package versions with the Neovim API version represented by the generated client.

Scope

• Publish the RPC client package as the main NuGet artifact.
• Stop treating the remote-plugin host as the primary published package.
• Align package versions with the Neovim API version used to generate the client.
• Use stable Neovim versions for stable package versions, for example 0.12.x.
• Use nightly/pre-release package versions for generated nightly clients, for example 0.13.x-pre<build>.
• Investigate CI automation for regenerating and publishing nightly client packages from Neovim nightly metadata.
• Document the versioning and publishing policy.

Acceptance criteria

• The RPC client is the primary package published to NuGet.
• Package versions correspond to the Neovim API version represented by the generated client.
• Nightly client versioning supports pre-release packages such as 0.13.x-pre<build>.
• CI feasibility for automatic nightly regeneration and publishing is documented or implemented.
• The publish workflow and release docs reflect the package/versioning policy.

Blocked by

• proposal: Re-architect RPC client generator around neutral model and emitter abstraction + Roslyn #31

[justinmk]

• Publish the RPC client package as the main NuGet artifact.
• Stop treating the remote-plugin host as the primary published package.

to be clear, having 2 packages is just unacceptable. we should only have 1 package. there's no reason to have 2.

[alsi-lawr]

• Publish the RPC client package as the main NuGet artifact.
• Stop treating the remote-plugin host as the primary published package.

to be clear, having 2 packages is just unacceptable. we should only have 1 package. there's no reason to have 2.

OK, maybe I'm not clear about what's meant by "package". There'll be the client generator, which is entirely internal to this repository, and the actual package (Nvim.Client -- the RPC client generated with the generator) that's put on Nuget.org. That's the proposed split. I admit the wording sounds like it'll be more than that.