store container ids into the DB
The controller identifies containers by their names (prod-job-XXXX-XXXX / prod-sandbox-XXXX) which is nicely human readable but this is a blocker for renaming webapps/users (or destroying a webapp and recreating another webapp with the same name).
The container names should just be indicative (and not be considered as a key), the association should be made by storing the container ID into the database. Thus it will be agnostic to the webapp name.
Related to #123: any unknown container (job or sandbox) should be detected and deleted immediately.