Update action remains visible after a successful container update

[DeepZone]

Summary

After a container update completes successfully and the replacement container is running, the UI continues to offer the same update until the user manually clicks Scan now.

Steps to reproduce

1. Run an update scan and identify a container with an available update.
2. Click the update action for the existing tag.
3. Wait until Container Pilot reports success and the replacement container is running.
4. Return to or refresh the container list without starting another scan.

Actual behavior

The update button remains visible and the container is still marked as having an update. Clicking Scan now refreshes the state and removes the button.

Expected behavior

After a successful manual or automatic update, Container Pilot should immediately refresh or invalidate the affected container's scan result. The update button must disappear unless a genuinely newer image is already available.

Suggested behavior

• Re-inspect the replacement container's local image digest after validation succeeds.
• Update or invalidate store.scans[containerName] before returning the successful update response.
• Refresh the affected UI row from the authoritative server state.
• Apply the same behavior to manual updates, automatic updates, and an explicit switch to latest.

Acceptance criteria

• A completed update removes the stale update action without requiring Scan now.
• The button remains only when the post-update registry comparison detects another different digest.
• Both manual and automatic update paths have regression coverage.