updating go version to 1.24

[JslYoon]

Description of Changes

updating go version 1.24

Related Issue(s)

devfile/api#1715

Acceptance Criteria

• Contributing guide

Have you read the devfile registry contributing guide and followed its instructions?

• [o] Test automation

Does this repository's tests pass with your changes?

• [o] Documentation

Does any documentation need to be updated with your changes?

• [o] Check Tools Provider

Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)

[thepetk]

According to the failing CI

ERROR: failed to build: failed to solve: registry.access.redhat.com/ubi8/go-toolset:1.24: failed to resolve source metadata for registry.access.redhat.com/ubi8/go-toolset:1.24: registry.access.redhat.com/ubi8/go-toolset:1.24: not found

I wasn't able to pull this image locally either

[Jdubrick]

/retest

[thepetk]

Btw I feel this one should be merged soon as I see there's an issue after this commit of the registry-support and the CI is failing

https://github.com/devfile/registry/actions/runs/16881295727/job/47817561251?pr=627

[JslYoon]

@thepetk @Jdubrick do you know where ci/prow/v4.16-registry-test CI is set up? Looks like I need to update its go version from 1.23 to 1.24

[michael-valdron]

@thepetk @Jdubrick do you know where ci/prow/v4.16-registry-test CI is set up? Looks like I need to update its go version from 1.23 to 1.24

@JslYoon You'll need to update this line to golang-1.24 and open a PR under openshift/release to change the CI runtime.

FYI you will need to do the same for the other OpenShift CI checks (for devfile/registry-operator and devfile/integration-tests) as well.

[thepetk]

@thepetk @Jdubrick do you know where ci/prow/v4.16-registry-test CI is set up? Looks like I need to update its go version from 1.23 to 1.24

@JslYoon You'll need to update this line to golang-1.24 and open a PR under openshift/release to change the CI runtime.

FYI you will need to do the same for the other OpenShift CI checks (for devfile/registry-operator and devfile/integration-tests) as well.

@JslYoon to add to michael's point you can take a look to a similar PR here: openshift/release#65672

[michael-valdron]

/retest

[michael-valdron]

/test all

[michael-valdron]

/lgtm

I would wait for @thepetk's approval as well.

[thepetk]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JslYoon, michael-valdron, thepetk

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [michael-valdron,thepetk]

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