Prevent post-install update entity flicker to “upgradable”

[Copilot]

After a container upgrade is triggered from the update entity, the entity could briefly return to on (update available) during the reload window before coordinator data settled. This change keeps the entity in an explicit install-in-progress phase until refreshed state is available.

• Update entity state sequencing

  • In DockerContainerUpdateEntity.async_install, in_progress now remains True until coordinator.async_request_refresh() completes.
  • The transition to in_progress=False is deferred to the finalization block after refresh, avoiding an intermediate stale “upgradable” presentation.

• Behavioral guardrail in tests

  • Added a unit test to assert that in_progress is still True while refresh is executing, and only resets afterward.

• Illustrative change

  try:
      await self.coordinator.create()
  finally:
      try:
          await self.coordinator.async_request_refresh()
      finally:
          self._attr_in_progress = False
          self.async_write_ha_state()

[gensyn]

@copilot Is an empty finally block in python valid and reasonable?

[Copilot]

Yes—try ... finally without an except is valid Python, and it’s commonly used for guaranteed cleanup. In this case the outer finally is not empty; it ensures we always run the post-install refresh/cleanup path even if create() raises.