create neovim plugins specific updater

[teto]

• init neovim plugin updater
• luarocks-packages-updater: convert into pyproject package
• pluginupdate: move to its own folder
• neovim-plugins-updater: 0.0.1
• moved .flake8 close to lua upadter
• fixup
• luaPackages: update on 2024-09-16
• renamed to nix_luarocks_updater
• luaPackages: update on 2024-09-18
• remove now unneeded override
• luaPackages: update on 2024-09-18

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[PerchunPak]

I am working now on reopening RFC 109 to standardize all updaters, but nice effort. I will look into it further later.

For now, could you describe design decisions made in this PR please? E.g. how did you solve the problem of two sources of truth that is described in #335931

[teto]

this was too complex. #344320 is more promising.