Update go version to 1.23.1

[dotNomad]

Used

go mod edit -go=1.23.1

Intent

Resolves #2268

Type of Change

• • Bug Fix
• • New Feature
• • Breaking Change
• • Documentation
• • Refactor
• • Tooling

[sagerb]

Had a concern regarding what was lost in the upgrade. Do we need to worry?

[dotNomad]

Had a concern regarding what was lost in the upgrade.

I re-did this commit without the go tidy so the indirect requires should no longer be removed.

[dotNomad]

Immediately got an error when trying to build with just the version upgrade:

go: updates to go.mod needed, disabled by -mod=vendor
	(Go version in go.mod is at least 1.14 and vendor directory exists.)
	to update it:
	go mod tidy

So re-added the go mod tidy.

@mmarchetti would you mind taking a look, and letting me know if I'm missing something in our Go version upgrade flow?

[mmarchetti]

go mod tidy removes what it thinks are unused packages. We're overriding the version of protobuf because github.com/spf13/afero's go.mod depends on a vulnerable version. This isn't the first vulnerable dependency afero has, and hasn't mitigated (there have only been 2 PRs merged this year in that repo). We might consider seeing if there's a fork that is better maintained, or fork it ourselves and updated the dependencies there.

[dotNomad]

Updated with a commit from @mmarchetti that updated the go.mod off of main and ran go mod vendor

[sagerb]

Upgraded to go 1.23.1 within VSCode and build runs successfully.