Consider renaming `options` option under `vim` to be named `opts`.

[vic]

Hello,

I'm the author of Den, after someone asking how to use NVF standalone with Den, I created an example for them, Den uses a deferred vim module, that will later be given to inputs.nvf.lib.neovimConfiguration

{
  vim.lazy.plugins = { ... };    # works 
  vim.options.expandtab = true;  # FAILS
}

The problem rises from vim being a deferred module, and NVF defining an option named options, our current workaround is to use

{
  vim.config.options.expandtab = true; # Explicit about `options` being a config value
}

However, given that NVF uses Opts suffix for things like plugin's setupOpts, I was wondering if it would be better for NVF to use vim.opts instead of vim.options.

Having an mkAliasOptionModule [ "opt" ] [ "options" ] would also work.

See vic/den#322 (reply in thread)

[NotAShelf]

I think we discussed vim.opt while the option was being added, but went with vim.options because opt would be inconsistent with globals. I think the cleanest approach here is adding the alias option for the sake of providing compatibility. I'll make the changes tonight, but I would be happy to review a PR today before I'm on my system.