clear containers or images - fuzzbench only or experiment only support

[zchcai]

Who is affected?

Machines have other docker containers running background, or have other images caches, not related to fuzzbench project.
Especially local runners and debuggers.

When does this need occur?

Run make clear-cache.

fuzzbench/Makefile

Lines 48 to 52 in ca24c30

	clear-cache:
	docker stop $$(docker ps -a -q) 2>/dev/null ; \
	docker rm -vf $$(docker ps -a -q) 2>/dev/null ; \
	docker rmi -f $$(docker images -a -q) 2>/dev/null ; \
	docker volume rm $$(docker volume ls -q) 2>/dev/null ; true

Also, there is need when doing local testing runs.

Expected behavior (i.e. solution)

Several thoughts and anticipations:

1. Separate stoping/removing docker containers with removing docker images caches.
2. Only clear/remove fuzzbench related docker images or containers.
3. Can provide options for experiment-specific docker containers stopping. This is important for local end-to-end testing, where docker runners have been started while that test is failed. We want to stop and remove docker containers only related to that test experiment.

Possible solution is similar to ones in #470. We may need to specify the experiment name or other identifiers when creating docker containers to run.

Other Comments

Related to #365 and #470.

[zchcai]

#470 vs #479
#470 is for local stopping logic. It may include more than stopping unfinished docker containers.
#479 is for a user-friendly option as make clear-cache. We may split that into two, and support experiment-level or fuzzbench-level only cleaning.