Code quality

[dorodere]

I wrote this when I freshly started with Rust, and let it largely rot until this very day. So the mistakes are exactly the ones made by someone who's still used to other flow structures:

• Run cargo clippy -- -Wclippy::pedantic and see the 60 things it yells about.
• Probably a lot of the actual functionality seperation could be redesigned. Like, all real routes go into a routes module, forwarding into a more typesafe machinery at some other level.

[dorodere]

Addtionally, we may want to consider to make the naming of the templates more consistent. There's drives-panel, superuser-panel and registrations-panel, but personcontrol is the odd one out.

[dorodere]

Rough, but more specific than above todo:

• [x] (low complexity) Run cargo clippy -- -Wclippy::pedantic and see what it wants from us, ideally silence it to 0 warnings. We're not running with an MSRV, but 1.65 should be safe to target since rustup is easy to acquire from anywhere
• [x] (low complexity) Remove the this. prefixes everywhere in the templates and make sure the UI still works
• [x] (low complexity) Rename the toggle-button CSS class to something more fitting, likely frameless or the like
• [x] (low complexity) Change the permissions of the source files to be consistent (644 for files, 755 for dirs?)
• [ ] Refactor the module structure to be actually sensible and navigatable
  • [x] (low complexity) Make the primary stuff a library crate and the binary crate just on top of it, making lib.rs containing only route accumulations/module inclusions and main.rs just a #[launch] nyooooooooom
  • [x] (medium complexity) Create a new directory + module routes, moving all routes in there, splitting properly again (so for example all the drives handling should be in a submodule of the superuser, which in turn again is a submodule of routes)
  • [ ] (medium/high complexity) Create a new directory + module sql_interface, which in turn again roughly contains one module for each table. The structs in there should be built in a pattern of Registration::query_for(person, drive) rather than loosely coupled functions. Creativity can come to play here, maybe we need some kind of pseudo-ORM for our stuff
  • [x] (low complexity) Give the drive validation functions a more reasonable place than directly in main.rs EDIT: Still in the now-moved dashboard.rs, but I can't think of a better place than directly where it is used.

[dorodere]

Work happens on the refresh-revamp-refactor branch.

[dorodere]

Fwiw after the rework, the backend will need to be launched with crates/backend as CWD.