Semiautomated distribution of LOVJ

[dag7dev]

As described here it is possible to release LOVJ as a single file instead of cloning the entire directory.

Since master is pushed only when the changes are considered enough "mature", we could provide to user a way to quickly run LOVJ.

One initial idea could be: everytime a push on main occurs, it creates a new release for windows (exe), linux (appimage), and macos (dmg).

Another idea could involve create a .love file in release.

Furthermore, we can think to do all of above.

For more information: https://github.com/love-actions everything is just there, we only need to better understand what to do and how users can load their patches (example, copy-paste each patch in the directory with the executable of LOVJ and LOVJ will take care of displaying user patches).

(I think this is a low priority issue and is nothing more than a brainstorming)

[merumerutho]

Interesting! Yes, this is going to be handled as low priority but it's definetely a good idea to improve deployment.