[FEATURE] Make it more difficult to accidently enable USE_PROXY_PROTOCOL

### What's needed and why?

It's too easy to enable USE_PROXY_PROTOCOL without understanding the consequences.

Setting this while messing with settings will likely result in the user loosing access to the web ui, forcing them to edit the database to recover.

### Implementations ideas (optional)

It would be nice to have a dialogue pop-up that explains the consequences of setting it (ie that if you're not using a reverse proxy you'll loose access to the web UI) and asks the user to confirm that's what they want.

Additionally, having a built in recovery mechanism that sets it to false would be nice. Something like a script in the docker container that can be run from a docker compose exec or similar.

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Start by locating the web UI control for USE_PROXY_PROTOCOL and the Docker container entry points available through docker compose exec. Review how settings are persisted and recovered; done means enabling the setting requires an explicit consequence warning and users have a documented way to restore it to false without editing the database.

Written by the indexing model from the issue text.