Optimize API Changes

[Tom-Szendrey]

Issue:

1. It is hard to follow what is going on as we are throwing all optimize interventions into one big blob.
2. Our optimize intervention type (find new start time, param value ect) was being incorrectly assigned when multiple types were given all but the first were ignored.

Description

• Re-organize how we are sending in the interventions to be optimized.
  • Rather than sending one big messy blob send a list of InterventionObjective
• Utilize intervention_func_combinator to allow us to intervene on two interventions with different types.
  • Previously if we sent the screenshot below both of the interventions were incorrectly using new start time
• Provide objfun our list of interventions to optimize over as in follow up PR we will be fixing and cleaning the logic written here but I do not want to flood this PR with more changes as it may become very hard to follow.
  The follow up PR will solve the issue that asking to optimize for start time AND value fails

Related Required:

DARPA-ASKEM/terarium#5360

Pictures

[liunelson]

Looks great - thanks for tackling this tricky feature. I see that you've covered the last-day vs. global max QoI, min vs. max objective function and the func_lengths details correctly (at least as far as I know).