Fix make ci-clean and runlocal-rp

[SudoBrendan]

Which issue this PR addresses:

Fixes local make errors

What this PR does / why we need it:

Problem 1: make runlocal-rp

Typo in image tag.

Problem 2: make ci-clean

Fix an error for orphaned running work containers by buildah that prevents prune from working. This can occasionally happen when you kill a build with ctrl-c (which can lead to some really wonky build states, like RUN commands missing the cache randomly/etc - make ci-clean needs to be capable of fixing these states):

$ make ci-clean
podman image prune --all --filter="label=aro-*=true"
WARNING! This command removes all images without at least one container associated with them.
Are you sure you want to continue? [y/N] y
Error: image used by fe1476ec4e2c451b5cdf0788df13f9006a64b4c7efa8cde43b72aec1f673c261: image is in use by a container: consider listing external containers and force-removing image
make: *** [Makefile:222: ci-clean] Error 125

Listing external containers, you can see the buildah working container artifacts that prevent image deletion:

$ podman ps --external
CONTAINER ID  IMAGE                                                                                          COMMAND     CREATED     STATUS      PORTS       NAMES
81b98b6b041d  registry.access.redhat.com/ubi8/nodejs-16:latest                                               buildah     4 days ago  Storage                 nodejs-16-working-container
3c1b2bf5c347  docker.io/library/46d89be108e7fa5cac82f7e68c543539b7c13e558ed1cdf78498b51916586f80-tmp:latest  buildah     4 days ago  Storage                 3d52b3bb3d8a-working-container
3efa745fabf8  docker.io/library/2aa66078bf34e95141549305672566212ddb4f66ba2fcce4a856e2bc1e199c4a-tmp:latest  buildah     4 days ago  Storage                 327bc823b740-working-container
3610dc395a7a  docker.io/library/cea1b1cccd979795295a974097fa8db114ac9ec5f125eafe5252865bf87ea16a-tmp:latest  buildah     4 days ago  Storage                 7b178c9a4c1f-working-container
eed2a06abda2  docker.io/library/11672cccafff0e2355b71f5458990cda5ad64035201a45e3923a3ae0ca924f6c-tmp:latest  buildah     4 days ago  Storage                 8a45bc60bb06-working-container
7fa4dba5db49  registry.access.redhat.com/ubi8/nodejs-16:latest                                               buildah     4 days ago  Storage                 nodejs-16-working-container-1

Unfortunately, I couldn't take "standard" routes:

1. podman system prune --external does not fix the issue
2. buildah rm -a would be nice, but buildah is strictly Linux and will not port to MacOs as part of make - so I had to build my own version of this command.

Test plan for issue:

Run make ci-clean locally, validate buildah containers are also removed with podman ps --external.

Is there any documentation that needs to be updated for this PR?

N/A

How do you know this will function as expected in production?

Does not affect production, only local image cache and containers created by buildah.

[SudoBrendan]

I seriously wish this command could be prettier - I went through many iterations before settling here. If podman rm --filter supported COMMAND, this would be trivial, but it doesn't, and /dev/null is required because make does weird things with STDOUT on $(shell) stuff (you get errors like <Deleted Container SHA>: command not found) :/

[kevinobriendotca]

We could shorten it a bit with command substitution.

podman rm -f $(podman ps | grep buildah | awk '{print $1}')

Also, podman rm has the -i flag that will ignore errors for non-existent containers and return 0 regardless of whether a container was deleted or not. Could possibly use that instead of the redirect to /dev/null.

Or, could we add a name to the build container so we can use the rm filter?

[SudoBrendan]

/azp run ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[rajdeepc2792]

I was not able to reproduce the issue with the orphaned running work containers at my side. But the make ci-clean works correctly.
MacOS.
LGTM.