Remove WorkoutController in favor of a Riverpod-based solution
The architecture of WorkoutController and associated classes is pretty hard to get oriented in, especially when it comes to how it manages state.
It'd be great to build a new architecture based on Riverpod to replace WorkoutController.