udt-migration: now supports reseda-rust backend with rebuilt api

[bennjii]

This pull request outlines the now required migration from reseda-server (deprecated) to the new reseda-rust (private) binding. The client will no longer support the reseda-server versioning, and now exclusively supports the rust implementation.

This brings the following benefits:

• Stably connects < 2s
• Improved status communication between services
• Consistent 0.2s uptime on the server for minimal outage possibilities
• Rust panic safety - Prevents unnecessary crashes or unexpected errors (safe code).
• Allows for real-time usage status updates to the user so they can know how much they are using and when.
• Reworked Connection and Socket API
  • Better handles connection and disconnection with greater understanding of system state and recoverability
  • Dynamic access of information for any implementation of UI which only needs to handle passing access to helper functions.

Note this change is non-backwards compatible and therefore requires migration to this version to further access any reseda run servers. As of this implementation, reseda-server has been made open source, however the implementation was both poor and non-performant. Furthermore, the rust implementation fixes many known security and QOL issues with the previous API. Now, connection is significantly simplified and dynamic server-side handlers organize and arrange wg connections with far greater thread and time-lock safety. This implementation prevents odd or un-diagnosable issues with cross-assignments or other odd issues that could have arisen with horizontal scaling. This new implementation also supports deep multithreading for both handling multiple incoming sockets, and for running background cron jobs to update users with their periodic usage statistics. All with the performance of the low level language; rust and its incredible memory safety.