Upgrade go version to 1.23

[thepetk]

Description of Changes

Simply upgrades the go version of alizer to 1.23

Related Issue(s)

partially fixes devfile/api#1671

Acceptance Criteria

Testing and documentation do not need to be complete in order for this PR to be approved. However, tracking issues must be opened for missing testing/documentation.

• Unit/Functional tests

• Documentation

Tests Performed

Explain what tests you personally ran to ensure the changes are functioning as expected.

How To Test

Instructions for the reviewer on how to test your changes.

Notes To Reviewer

Any notes you would like to include for the reviewer.

[thepetk]

Note: Once merged we'll need to cut a new release with version v1.7.0

[Jdubrick]

Overall looks good, I noticed it seems like there is some old commits in this PR - I wonder if the branch needs a rebase?

[thepetk]

Overall looks good, I noticed it seems like there is some old commits in this PR - I wonder if the branch needs a rebase?

yeah I cleaned my main branch in my fork a bit

[Jdubrick]

lgtm, failing check for scoreboard is automatic because of a deprecated dep so we'll need an issue opened to address that. I can open the issue for it fyi @thepetk

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Jdubrick, 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 [Jdubrick,thepetk]

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

[openshift-ci]

New changes are detected. LGTM label has been removed.

[thepetk]

lgtm, failing check for scoreboard is automatic because of a deprecated dep so we'll need an issue opened to address that. I can open the issue for it fyi @thepetk

I've bumped up for alizer to v4.6.0 but I do feel an issue needs to be created as we'll need to do this across all our repos

[Jdubrick]

lgtm, failing check for scoreboard is automatic because of a deprecated dep so we'll need an issue opened to address that. I can open the issue for it fyi @thepetk

I've bumped up for alizer to v4.6.0 but I do feel an issue needs to be created as we'll need to do this across all our repos

devfile/api#1675 for reference