criu_test should run with podman (not docker)

Got the following error when running dev.external ([internal/Grinder](https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder/31504/console))

```
00:02:15.813 build_image:
00:02:15.813 [echo] Executing external.sh --build --dir functional-test --tag nightly --version 11 --impl openj9 --docker_args
00:02:15.813 [exec] The test here is functional-test
00:02:15.813 [exec] The directory in the external.sh is functional-test
00:02:15.813 [exec] DOCKERIMAGE_TAG nightly has been recognized.
00:02:15.814 [exec] build_image.sh functional-test 11 openj9 ubuntu jdk full linux_x86-64 0
00:02:15.814 [exec] /home/jenkins/workspace/Grinder/aqa-tests/external
00:02:16.258 [exec] Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
00:02:16.258 [exec]
00:02:16.258 [exec] Writing /home/jenkins/workspace/Grinder/jvmtest/external/functional-test/dockerfile/11/jdk/ubuntu/Dockerfile.openj9.full ... done
00:02:16.258 [exec]
00:02:16.258 [exec] The test in the build_image() function is functional-test
00:02:16.258 [exec] #####################################################
00:02:16.258 [exec] INFO: docker build --no-cache -t adoptopenjdk-functional-test-test:11-jdk-ubuntu-openj9-full -f /home/jenkins/workspace/Grinder/jvmtest/external/functional-test/dockerfile/11/jdk/ubuntu/Dockerfile.openj9.full /home/jenkins/workspace/Grinder/jvmtest/external/
00:02:16.259 [exec] #####################################################
00:02:16.259 [exec] time="2023-03-09T07:28:54-08:00" level=warning msg="RunRoot is pointing to a path (/run/user/1000/containers) which is not writable. Most likely podman will fail."
00:02:16.259 [exec] Error: error creating tmpdir: mkdir /run/user/1000: permission denied
00:02:16.259
```

criu_test should run with podman (not docker).

I think the problem is that `criu_test` is under `functional-test` folder and `functional-test` is also considered the test name. And podman is only set for test names containing criu.
Not sure if it is easier to move `criu_test` into the existing criu test folder.

related: https://github.com/adoptium/aqa-tests/pull/4376

Start by reading external.sh and build_image.sh, then trace how criu_test is identified under functional-test and compare that with the existing criu test folder. Run dev.external in the affected environment and verify that criu_test invokes podman without the /run/user/1000 permission error; the related pull request may provide context.

Written by the indexing model from the issue text.