Luarocks: Cleanup

The formula is a mess. I’m not sure why the stable block was necessary any more, upstream aren’t going to move on the install target check so there’s no risk of the patch becoming obsolete any time soon.

This PR is pretty much just to make reading the Luarocks formula a little more pleasant for everyone (And me). Nothing more fancy than that for now.

It also turns out Luarocks is using the system OpenSSL to check download MD5Sums. I’m not sure whether this merits an additional dependency or not. My gut says no, but equally I squirm at using the system OpenSSL for anything. I’ll leave the OpenSSL point open to discussion. Meh.

(*Side note - Why are you still using MD5Sums Luarocks? Seriously?*)
With the last release I just ended up kinda updating the patch's language and keeping it, because upstream hadn't changed the language in that section appreciably. What I'd really love to see from upstream is a ``` ./configure ``` option along the lines of ``` --no-check-permissions ``` but I don't know if we'd get that.

Theoretically, we could do away with the patch and just let Luarocks run the check, since it should run without issue because we ensure the directory is user-writable before we use it, but in reality it has flagged false positives before and that's caused issues.