GSF-12 IndependentActionAdapterManagerBase fixes

[StephenCWills]

The queue of input measurement keys was unnecessary, because the synchronized operation was copying the reference to a local variable anyway. However, by keeping an old collection of input measurement keys in the queue, the adapter is much more likely to use an old collection of inputs against an updated DataSource leading to mismatches.

---

If you specify inputs manually by signal ID, InputMeasurementKeys might end up with a measurement key for an inactive measurement. This results in an error:

Failed to initialize adapter OSCILLATIONTEST!44291B81-4467-4A33-BD1A-6C19473BFD99: Cannot use NONE as input to frequency based oscillation detector. One voltage angle input measurement is required. Cannot initialize adapter.

By filtering inactive measurements early, we avoid these types of errors. We also avoid potential desyncs between the base class and the subclass during initialization. It's unlikely that an adapter developer would want an inactive measurement in their adapter, since they can't even query metadata for it from ActiveMeasurements.

---

The bulk calculation adapter updates its configuration whenever the DataSource is updated. If a child adapter was already initialized in a prior configuration update, the child adapter will be skipped and the adapters collection can no longer be used to reliably determine what the CurrentAdapterIndex is.

As an example, consider the case where ADAPTER1 is at index 0 and ADAPTER2 is at index 1. If you enable ADAPTER2 after the bulk calculator was already initialized, the child adapter for ADAPTER1 would already be initialized. Therefore, initialization of the child adapter for ADAPTER1 would be skipped, and adapters.Count is still 0. When initializing the child adapter for ADAPTER2, the base class informs the subclass that CurrentAdapterIndex is 0 so the subclass mistakenly returns the device ID for ADAPTER1.

[ritchiecarroll]

Changes look simple enough, but I have not tested - presume you have - so approving on that condition.

[StephenCWills]

Yeah, I couldn't even figure out what the problem was without extensive testing. 😩