fix: Clear the initialized condition state when the card is not usable (#2646)

The `initialized` state (used in conditions/triggers) was written once
and never cleared, so it meant "has this card ever been initialized"
while everything reading it took it as "is this card usable now". Home
Assistant takes a card off the page and puts it back whenever its
dashboard tab is left and returned to, so the card initialized again
while the state claimed it was initialized throughout: `trigger:
initialized` fired once per card rather than once per startup, and
automations were dropped in between.

The card lifecycle is now an explicit state machine (`SessionManager`),
the only writer of `initialized`, which separates a card that is
starting up from one initializing part of itself again while it runs. A
new `ever` parameter (conditions/triggers) selects the old latched
behaviour.

`remote_control` uses that parameter to keep its two camera priorities
correct under repeated starts. With `camera_priority: entity` the card
now re-reads the entity every time it starts, so a camera selected while
the card was away is picked up on return. With `camera_priority: card`
the card writes the entity on its first start only, unchanged, since
repeating that write would overwrite a camera the user had selected.

Closes: #2642


BREAKING CHANGE: `condition: initialized` is now `false` whenever the
card is not usable, and `trigger: initialized` fires each time the card
starts up rather than only the first time. Set `ever: true` on either to
keep the previous behaviour.

src/card-controller/automations-manager.ts

@@ -56,7 +56,7 @@ export class AutomationsManager {
       // automation once initialization completes so that the trigger evaluators
       // baseline their initial pre-trigger value against a card whose template
       // renderer has loaded.
-      if (this._api.getInitializationManager().isInitializedMandatory()) {
+      if (this._api.getInitializationManager().areMandatoryAspectsInitialized()) {
         triggers.subscribe();
       }
     }
@@ -83,7 +83,7 @@ export class AutomationsManager {
       // Never execute automations if the card hasn't finished initializing, as
       // it could cause a view change when camera loads are not finished.
       // See: https://github.com/dermotduffy/advanced-camera-card/issues/1407
-      !this._api.getInitializationManager().isInitializedMandatory() ||
+      !this._api.getInitializationManager().areMandatoryAspectsInitialized() ||
       // Never execute automations if there's an error (as our automation loop
       // avoidance -- which shows as an error -- would not work!).
       this._api.getIssueManager().getStateManager().hasFullCardIssue()