chore: publish native image docker images from java-shared-config

[mpeddada1]

Verified with https://github.com/mpeddada1/test-graalvm-cloud-build

• Docker images for graalvm 22.3.2 JDK 11 and graalvm 22.3.2 JDK 17.
• Cloud Build presubmit check has been set up in the cloud-devrel-kokoro-resources GCP project to verify the docker image build locally.
• Cloud Build trigger has been set up in the cloud-devrel-kokoro-resources GCP project to publish the docker image to cloud-devrel-kokoro-resources and cloud-devrel-public-resources upon merge of .kokoro/docker/ update PRs into themain branch.

In next PR:

• Updated Kokoro Downstream checks to use newly published images.
• Add release blocking Kokoro check to verify presence of the docker images.

[burkedavison]

Nice updates! Thanks

[mpeddada1]

@suztomo Wanted to call out these publishing destinations. We're publishing to gcr.io/cloud-devrel-kokoro-resources/ which will be used by our kokoro jobs downstream and gcr.io/cloud-devrel-public-resources which is a public repository of images for client library testing.

[suztomo]

Do you need both? Can you write down rationale in source code comments in this YAML file?

[mpeddada1]

I think gcr.io/cloud-devrel-kokoro-resources is used by Kokoro jobs whereas gcr.io/cloud-devrel-public-resources/ is used for making our testing images public to allow non-Googlers to run tests against the same image as us. I've added this in here following convention in https://github.com/googleapis/testing-infra-docker. We seem to publish images to both locations for several other languages as well (nodejs, python). Example: https://github.com/googleapis/testing-infra-docker/blob/f3a27546b3a9fedef75a78f22c8fde23d5c013d3/python/cloudbuild.yaml#L61-L69

[suztomo]

I see it uses Cloudbuild, not Kokoro. So don't use ".kokoro" directory.

[mpeddada1]

The dependencies (11) job is stalled for some reason. It was recently removed in #655 but still specified here