Privacy options for user information

[kinn-edendev]

Currently the labmap shows a small log of whoever logs into a machine. This has been brought up as a minor privacy concern, and although the OCF doesn't make promises of anonymity when entering and using the machines, I still think it would be worth creating a way for users to choose whether or not they want their users to appear logged-in when using the machines.

The username tracking is a core feature of the labmap2, and removing the usernames appearing entirely would effect the use in future stages of the project such as custom waddles sprites. For those who don't want to appear, there are a couple settings I propose which could offer that kind of support. All of which are proposed continue to gather usernames on the backend level before the DGS gathers information from Prometheus.

1. Default "show username and sprite" setting on the proposed Art Server. By default, user's custom sprites and username will appear on the labmap, that way we can maximize activity on the labmap.
2. "Hide username and show sprite" setting. This setting would likely have to use some way of obfuscating the username as it appears, maybe setting it to a randomized username or using a placeholder like "anonymous waddles" while maintaining the custom sprite. This gets a little tricky as we'll have to use a different metric like a user ID which can accurately track who's who without revealing said information on the API (which is still public, btw).
3. "Hide username and sprite" setting. This option, on it's most basic level just spawns a waddles to go sit at a computer with no username/random username/placeholder appearing in the log, and then spawn a randomized/default waddles to go sit at the computer. This just shows the computer is occupied and nothing else and can be achieved with the basic "logged_in" and "user" fields already collected on the labmap.
4. "Show no activity/stealth" setting. This setting will never show any activity from your user when using the desktops. You can be fully logged in and it won't show your name in the logs nor will it spawn a waddles to go sit at your desktop.

All these proposed changes will have to occur on the DGS level using some processing of the data_generator.py script where it will first read the name of the user logged in from Prometheus, then check against the Art Server for that user's settings and then produce the correctly formatted data for interpretation by the Labmap godot client. This also goes under the assumption that the DGS API remains public, which I think should remain that way so we don't have to embed secrets in the clients (an unsafe practice).