Reorganize Pyomo control rule classes

Reorganize Pyomo control strategy classes

The file h2integrate/control/control_strategies/pyomo_controllers.py has 3 controller strategy classes (and soon more as PR #407 is merged in) with varying level of inheritance that makes it difficult to follow the logic that distinguishes the individual control strategies. I think that the baseclasses should only include methods that are fully used across all controllers that inherit it, without any excess logic that is specific to a single controller.

I also think that the controller baseclass in h2integrate/control/control_strategies/controller_baseclass.py could be removed and be replaced with the PyomoControllerBaseClass.

I almost think it'd be nice to split out these controllers into separate files. Like PyomoControllerBaseConfig and PyomoControllerBaseClass (maybe even SolverOptions if that's used across the Pyomo controllers) could be moved into h2integrate/control/control_strategies/controller_baseclass.py. Then separate files for SimpleBatteryControllerHeuristic, HeuristicLoadFollowingControllerConfig and HeuristicLoadFollowingController, and OptimizedDispatchControllerConfig and OptimizedDispatchController.

Start by reading h2integrate/control/control_strategies/pyomo_controllers.py and controller_baseclass.py, then compare the three controller strategy classes and their shared methods. Review the proposed PyomoControllerBaseConfig, PyomoControllerBaseClass, and SolverOptions organization, including the controllers named in the issue. Done means the inheritance and file layout clearly separate shared logic from controller-specific behavior without changing strategy behavior.