controller scheduler rewrite

• focus on two controllers: scanner and tracker
• re-write scans to be just functions - scan always has a cycle and is deterministic (even when its random)
• use the scan function with the scanner controller (somehow?) to define the radar behavior
• controller has: time-slice, what static parameters gets set, what mutable parameters gets set during run - useful meta data to have
• controller will do: be able to generate a table with time-slices and values for all parameters on demand (how is the table size decided? time-delta? number of slices? both?)
• somehow update the controller parameters that actually decide what is output by the table generation
• while writing the scheduler - see if cleaner / easier to optimize / memory is a problem - maybe just have a pre-defined list of all parameters that can get modified and these are just always the columns of the table
• pre-defined list start: coh_int_bandwidth, pointing, ipp, pulse_length
• tracking controller should take a pass and generate the table
• the scheduler should take controller, parameters for the scheduling, and generate a master table
• move the "observed parameters scheduler" away for now - refactor once table generation by scheduler is done

for now - tables = pandas dataframe