Allow changing the default expected state of `ToggleableService`
Some services can be managed by both region and rack, with the latter
being in control for rack-only deployments. In order to achieve that, a
layer of logic implemented in `RackOnlyExternalService` class checks the
deployment type and decides whether rack should control the service
state or not (service expected status = ANY). Once it have a decision,
the expected state of the service is updated by calling the appropriate
method of `ToggleableService` instance for the corresponding service.
However, this logic needs some time before the expected state is updated.
Since the current default expected service state is `SERVICE_STATE.OFF`,
in rack+region deployments, rack will try to bring the services down
until `RackOnlyExternalService` instance updates the state, while region
will bring the services back online. The side effects of such races are
devastating to some services, especially ones that have cleanup steps in
their startup shell script.
The proposed solution is to have the affected services default expected
state as `SERVICE_STATE.ANY` to prevent rack from bringing them down.
Update maas-ui to 9074ea68b
feat: tag management panel MAASENG-1427 (#5051)
- remove .l-aside visibility workaround
- refactor AppSidePanel
- update node action menu dropdown styles
- remove eslint-disable-next-line cypress/no-force comments as we disable the rule globally due to vanillaframework implementation of form elements
