Add testcontainers/ryuk docker image to the allowed images list

[linghengqian]

What does this PR do?

• For Add support for io.etcd:jetcd-core:0.7.5 #170 and Add support for io.etcd:jetcd-core:0.7.5 #164.
• Fixes Enable testcontainers tests once ryuk docker image is replaced with some less vulnerable  #250.
• Add testcontainers/ryuk docker image to the allowed images list.

$ grype testcontainers/ryuk:0.5.1
✔ Vulnerability DB        [updated]
 ✔ Parsed image            
 ✔ Cataloged packages      [27 packages]
 ✔ Scanning image...       [4 vulnerabilities]
   ├── 0 critical, 2 high, 2 medium, 0 low, 0 negligible
   └── 2 fixed
NAME          INSTALLED  FIXED-IN   TYPE  VULNERABILITY  SEVERITY 
libcrypto1.1  1.1.1t-r2             apk   CVE-2023-0466  Medium    
libcrypto1.1  1.1.1t-r2  1.1.1u-r0  apk   CVE-2023-2650  High      
libssl1.1     1.1.1t-r2             apk   CVE-2023-0466  Medium    
libssl1.1     1.1.1t-r2  1.1.1u-r0  apk   CVE-2023-2650  High

Checklist before merging

• I have properly formatted metadata files (see CONTRIBUTING document)
• I have added thorough tests. (see this)

[linghengqian]

• Call @matneu to help with the review.

[matneu]

Based on the testcontainers information here, ryuk has to run privileged, which is a no-go for us.

[linghengqian]

• @matneu Does the project allow global setting of .env file, in which TESTCONTAINERS_RYUK_DISABLED=true is configured by default? This will avoid the tedious setup of each test folder.

[dnestoro]

@linghengqian we cannot allow global .env for docker images. Please close the PR unless you have some other idea how to solve this

[linghengqian]

@linghengqian we cannot allow global .env for docker images. Please close the PR unless you have some other idea how to solve this

• @dnestoro I have another question, are .env files allowed to exist in submodules where unit tests are located? The Contributor Guidelines don't make this clear.

[dnestoro]

@linghengqian local env file is okay. We cannot allow global env files, but as long as you are affecting only your test, it is okay. Anyway, even with the env variable, do you still need this docker image for your test? If so, then @matneu can we accept this docker image if it is not run as privileged container?

[linghengqian]

@linghengqian local env file is okay. We cannot allow global env files, but as long as you are affecting only your test, it is okay. Anyway, even with the env variable, do you still need this docker image for your test? If so, then @matneu can we accept this docker image if it is not run as privileged container?

• Thanks for the clarification. I will use a local .env file to introduce the use of testcontainers in the relevant unit tests of jetcd-core. This PR will be closed.