Allow reset the status of the containers

### Describe the solution you'd like

Good day, we have our Karavan pod only available in the mornings to save costs, but after one of our drops of a Pod has failed, and because the cache layer, we can't tell Karavan than that Pod was deleted, because Karavan try to delete it but failed with 404 and refuse to delete it from cache.

We could simplify this by having a "reset" button that forces the Karavan to drop the container status cache and re-sync with the Kubernetes or the Docker

### Variant

Web Application

### Container Management (if applicable)

None

### Operating System (for VS Code Extension)

None

Start by tracing how the web application caches container status and re-syncs with Kubernetes or Docker, then locate the container-management UI entry point. Define the reset action so it drops the cached status and confirms that the next synchronization reflects the actual container state.

Written by the indexing model from the issue text.