Install jq in gcb-docker-gcloud image

[ArkaSaha30]

This commit will install jq in gcb-docker-gcloud image so that the utility is available for all cloudbuild.yaml

Fixes: kubernetes/kubernetes#131257
Ref Discussion: kubernetes/kubernetes#131258 (comment)

Built and locally tested:

arkas1@arkas1-ubuntu-vm:~/test-infra/images/gcb-docker-gcloud$ docker run -it --rm gcb-docker-gcloud:latest 
1ebeb22425f4:/workspace# jq
jq - commandline JSON processor [version 1.8.0]

Usage:	jq [options] <jq filter> [file...]
	jq [options] --args <jq filter> [strings...]
	jq [options] --jsonargs <jq filter> [JSON_TEXTS...]

jq is a tool for processing JSON inputs, applying the given filter to
its JSON text inputs and producing the filter's results as JSON on
standard output.

The simplest filter is ., which copies jq's input to its output
unmodified except for formatting. For more advanced filters see
the jq(1) manpage ("man jq") and/or https://jqlang.org/.

Example:

	$ echo '{"foo": 0}' | jq .
	{
	  "foo": 0
	}

For listing the command options, use jq --help.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ArkaSaha30
Once this PR has been reviewed and has the lgtm label, please assign cjwagner for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[BenTheElder]

I'm not sure if this is the right approach.

We want to be able to build locally too, and this image is minimal containing docker-cli (so you can docker run) and gcloud (so you can upload results to the staging locations).

I don't think we should extend this image.

We could probably docker run jq in the build? (we should also obtain this via digest)

[BenTheElder]

If we do do this, we should at the very least be doing an integrity check (we should be for the others already here but that's not related to this PR), if not pinning the hash outright

[ArkaSaha30]

We could probably docker run jq in the build? (we should also obtain this via digest)

Are you suggesting something like this for all uses of jq in Makefile?

BASE.windows := mcr.microsoft.com/oss/kubernetes/windows-pause-image-base:v0.4.1@sha256:37cc10768383b55611d724a05eb18564cb5184c89b0c2faa7d4eff63475092df

JQ_IMAGE := ghcr.io/jqlang/jq@sha256:a186dcd84a1e28bb48cdf3d7768b890d08621a87bb651fadb7db6815a6bf5ad5

ALL_OSVERSIONS.windows := $(shell docker manifest inspect ${BASE.windows} | docker run --rm -i ${JQ_IMAGE} '.manifests' | jq -c '.[]' | jq '.platform."os.version"' | tr -d '"')

[BenTheElder]

Yeah that could work, right? Also means we control the jq version inline for any compat issues.