[CI]: support luarocks/rocks.nvim

[mrcjkb]

Hey 👋

Summary

This PR is part of a push to get neovim plugins on luarocks.org.

See also:

• rocks.nvim, a new luarocks-based plugin manager.
• this blog post.

Things done:

• Added a workflow that publishes tags to luarocks.org when a tag or release is pushed.
• Added note about using with rocks.nvim to the readme

See also: this guide

Notes:

Important

• For the luarocks workflow to work, someone with a luarocks.org account will have to add their API key to this repo's GitHub actions secrets.

• Tagged releases are installed locally and then published to luarocks.org.
  • If you push tags from a local checkout, the workflow is triggered automatically.
  • If you use GitHub releases to create tags, you may need to add a PA token for the workflow to be triggered automatically.
• Due to a shortcoming in luarocks.org (label doesn't get picked up from rockspec luarocks/luarocks-site#188), the neovim and/or vim labels have to be added to the luarocks package manually (after the first upload), for this plugin to show up in https://luarocks.org/labels/neovim or https://luarocks.org/labels/vim, respectively.

Once merged, you may need to run the workflow on the latest tag manually.

[udayvir-singh]

@mrcjkb This will take some time for me to review. I don't know why I would want to do automate deployment to luarocks, because there are times when I want to manually edit the tag's position in the git logs.

I am not going to add a CI step for luarocks, but I will upload to luarocks manually on time for v3 release.

Since, I'm on a break from development for this plugin, I will probably rewrite tangerine at the end of this year.

[mrcjkb]

Alright. I will add it to the NURR for now, and publish it with the neorocks account (as well as hibiscus.nvim).

Ping me if/when you are ready to publish it yourself, and I will delete it.

[udayvir-singh]

@mrcjkb Thanks.