If a collection is in a deactivated state, we want to remove the side effects of calculation and ignore it from future recalculation.
This will impact isolation boundaries as well, since they should effectively be removed- reactivating a collection should then result in the isolation boundaries being recalculated.
Maybe configure this from a state-level config screen such that recalculation on change doesn't kick in when toggling multiple collections on and off.
If a collection is in a deactivated state, we want to remove the side effects of calculation and ignore it from future recalculation.
This will impact isolation boundaries as well, since they should effectively be removed- reactivating a collection should then result in the isolation boundaries being recalculated.
Maybe configure this from a state-level config screen such that recalculation on change doesn't kick in when toggling multiple collections on and off.