[Bug]: Test container leak

### What happened?

THere are many stale containers generated every day and staged in GCR

- For Java tests, there is a clean up script https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/scripts/cleanup_untagged_gcr_images.sh run after each postcommit. However it seems there is still leftovers
- For Pyhon&Go ARM tests, afaik it does not remove stale container after test run

Also, I am not sure the Python ARM test ever use the container for dataflow tests: it pushes image: https://github.com/apache/beam/blob/a221f98a5f46be985afcb98a65fcec3b46b81f92/sdks/python/test-suites/dataflow/common.gradle#L149

but the later test is not referring the container pushed to GCR, and just uses beam-master one

### Issue Priority

Priority: 3 (minor)

### Issue Components

- [ ] Component: Python SDK
- [ ] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam YAML
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner