Add BASE_DOCKER_REGISTRY_CREDENTIAL_ID for external-test

[LongyuZhang]

• BASE_DOCKER_REGISTRY_CREDENTIAL_ID is needed to increase daily image pull limit when running container-based external testing
• Related Issue: runtimes/backlog/issues/1234

[github-actions]

Thank you for creating a pull request!

Please check out the information below if you have not made a pull request here before (or if you need a reminder how things work).

Code Quality and Contributing Guidelines

If you have not done so already, please familiarise yourself with our Contributing Guidelines and Code Of Conduct, even if you have contributed before.

Tests

Github actions will run a set of jobs against your PR that will lint and unit test your changes. Keep an eye out for the results from these on the latest commit you submitted. For more information, please see our testing documentation.

In order to run the advanced pipeline tests (executing a set of mock pipelines), it requires an admin to post run tests on this PR.
If you are not an admin, please ask for one's attention in #infrastructure on Slack or ping one here.
To run full set of tests, use "run tests"; a subset of tests on specific jdk version, use "run tests quick 11,21"

[LongyuZhang]

@AdamBrousseau Could you review it? Thanks.

[AdamBrousseau]

So I think if you add the dockerCredential lines to the specs you are running External tests then this PR should be fine.

[LongyuZhang]

dockerCredential lines have been added to z/p linux on JDK 11, 17 and 21 as suggested. Thanks.

So I think if you add the dockerCredential lines to the specs you are running External tests then this PR should be fine.

[llxia]

BASE_DOCKER_REGISTRY_CREDENTIAL_ID is set above, but we are using BASE_DOCKER_REGISTRY_URL_CREDENTIAL_ID here (which is not being defined)