Add mDNS support, so we can connect to e.g. `ftcscoring.local` rather than an IP

**Is your feature request related to a problem? Please describe.**
I run the event livestreams for my local league. Part of that includes using the live scoring overlay provided by the scoring software. Each event, to get the IP needed to connect, I need to either:

- Bother the refs/scorekeepers to get the IP address
- Use `nmap` to port scan all devices on the local network for any devices that have port 80 open, then try to connect to each of them until I find the correct one

**Describe the solution you'd like**
The software's web server should advertise itself via mDNS, so I can just navigate to e.g. `ftcscoring.local` without having to know the IP. This would fix the issue for me, and also make connecting easier for everything else (scorekeeping tablets, etc) as well.

**Describe alternatives you've considered**
I can't think of any better alternatives, broadcasting on a `.local` is pretty standard for any software that runs an HTTP server for use within a local network.

**Additional context**
I don't know if it's common to run two instances of the scoring software on the same network, but if so, care should be taken to avoid conflicts. Perhaps e.g. when starting up the server, check if `ftcscoring.local` is in use, and if so, use `ftcscoring2.local` instead, and so forth.