Wings: Add "wings reload-tls" subcommand to reload SSL certificate without restarting

[JrouleEnGolf5]

Problem :
In production environments where Wings shares a server with an existing web server (Apache, Nginx, etc.) occupying port 80, the --auto-tls flag is not usable because the ACME HTTP-01 challenge requires exclusive access to port 80.
The only current option with manual TLS is to run systemctl restart wings after renewing certificates. However, restarting Wings stops all running game server containers, which is completely unacceptable on 24/7 production nodes hosting live servers with active players.
Issue #2140 was closed by suggesting --auto-tls as the solution, but this does not address environments with an existing web server occupying port 80.

Solution :
Add a wings reload-tls subcommand to the Wings binary that reloads the TLS certificate from disk without restarting the process or stopping any containers.
This would allow a clean and simple certbot deploy hook:

bash# /etc/letsencrypt/renewal-hooks/deploy/wings.sh
wings reload-tls

Automatic renewal, zero downtime, no game servers interrupted.

Thank you for considering this request, I hope it can be implemented to improve Wings for production environments.

[DaneEveritt]

It should not be stopping running containers. Whatever was running when wings is stopped continues to do so, you just temporarily lose access via the panel until it comes back online and reconnects to the instances.

[JrouleEnGolf5]

I need to investigate why I lose my containers when I restart the Wings service.

However, from what I understand, I could configure Wings to restart automatically whenever the SSL certificate is renewed.

Thanks you for answer :)