Chore/upgrade go version

[PushparajShetty]

Description of your changes

How has this code been tested?

Checklist

I have:

• Title of the PR starts with type (e.g. [Addon] , [example] or [Doc]).
• Updated/Added any relevant documentation and examples.
• New addon should be put in experimental.
• Update addon should modify the version in metadata.yaml to generate a new version.

Verified Addon promotion rules

If this pr wants to promote an experimental addon to verified, you must check whether meet these conditions too:

• This addon must be tested by addon's e2e-test to guarantee this addon can be enabled successfully.
• This addon must have some basic but necessary information.
  • An accessible icon url and source url defined in addon's metadata.yaml.
  • A detail introduction include a basic example about how to use and what's the benefit of this addon in README.md.
  • Also provide an introduction in KubeVela documentation.
  • It's more likely to be accepted if useful examples provided in example dir.

---

Summary by cubic

Upgraded the Go version in go.mod from 1.22.0 to 1.23.8 to use the latest language features and improvements.

[cubic-dev-ai]

cubic found 1 issue across 1 file. Review it in cubic.dev

_{React with 👍 or 👎 to teach cubic. Tag @cubic-dev-ai to give specific feedback.}

[FogDong]

Can you sign the DCO?

[PushparajShetty]

Can you sign the DCO?

Hi @FogDong
I’m encountering some issues upgrading the Go version—right now, go mod tidy fails even on the master branch. It looks like more extensive changes are needed.
I’ll close this PR for now and reopen once everything is working properly.
Thanks