Provide a static library

[yd278]

Hi!
I have a few improvement ideas and would like to contribute them as a small series of focused PRs. Before I start, I want to confirm there’s no conflict with your roadmap or upcoming plans.

Proposals:

1. Publish prebuilt binaries in GitHub Releases (similar to how blink.cmp does).
2. Integrate the ime package into the codebase, so end users don’t have to build it separately.
   (These two remove the local build step, which makes the plugin easier to manage with plugin managers like lazy.nvim.)
3. Provide a simple configuration interface, e.g., setup(opts).

If this direction sounds reasonable, I can open these as separate PRs in the order above. I’m also happy to adjust the approach (e.g., make ime optional, use a submodule, or start with just releases) based on your preferences.

[Freed-Wu]

1. A better solution is to provide a website like luarocks: https://lux.lumen-labs.org/rocks-binaries/ or https://texrocks.readthedocs.io/ However, if it only host one plugin, it is too big. It is different from https://github.com/saghen/blink.cmp , blink.cmp use rust, which encourage static link, not dynamic link. If we provide a library, I think it should be static linked. We can provide static library, however we shouldn't disable how to build DLL. which distribution packager encourage it.
2. integrate ime is hard, due to many lua libraries need it. if you means copy ime to packages/ime/ may be possible. provide a static linked binary without break the building of DLL is possible, although I am not sure the potential difficulty. You can let user copy static library and other runtime dependencies like ime, platformdirs, ... to lua/ directory, which is just doned by a bash script to call curl/wget to download some files.
3. now we provide require'rime.nvim'.rime = cfg. What is the difference from setup(cfg)?

[Freed-Wu]

Now we provide a luarocks server. See https://github.com/rimeinn/rime.nvim#rocksnvim