Sb roi handles

[samiebee43]

Attempting to save spectra on mzieg-roi-handles created an error message. This happens because Measurement is relying on Multispec to carry a reference to Graph. The solution was to give Measurement a ctl parameter so it can reference Graph directly.

With this comes some more refactoring. Any class that depends on a live instance takes a ctl parameter, including ColumnFileParser which depends on a save_options and a measurements instance. Self contained classes such as DashFileParser do not need (and should not have) the ctl parameter.

Measurment gets a ctl parameter as well as some other parameters. Only the save_options and measurements fields were removed. MeasurementFactory keeps some of it's copied references not because that's the ideal state, but to limit the scope of this PR. That class has ctl tacked along with the other parameters (redundant).

Remember any time you inherit from an object you can simply omit inheritance for the exact same meaning. Object is inherited by default.

[mzieg]

Any interest in just giving Controller a static get_instance() method so that any code in ENLIGHTEN can just grab their own Controller instance anytime they want, and we won't need to keep passing it around?

Good refactor. Apologies for trying to merge code that clearly wasn't ready.

[samiebee43]

Yes that would be interesting.

One possible downside is that no longer would classes be identified as self-contained or not. For instance ColumnFileParser is not self contained because it takes a ctl param and depends on some Enlighten instances, but DashFileParser is self contained and can be trivially copied to another program.

But generally yes, in fact that would make Enlighten more compliant with Enlighten Extended Development section 4.4.