Spike: Investigate maintaining Go modules at the latest go version

[michael-valdron]

Which area/kind this issue is related to?

/area api /area library /area registry /area alizer /area integration-tests /area test-automation

Issue Description

With Go versions only on a two major release lifecycle it is important when managing dependencies to keep up to date with the Go version. Investigate which Go modules can be maintained at the latest Go version and which ones should be long-term fixed.

Acceptance Criteria

• [ ] Findings for devfile/api
• [ ] Findings for devfile/library
• [ ] Findings for devfile/integration-tests
• [ ] Findings for devfile/registry (test modules)
• [ ] Findings for devfile/registry-support/registry-library
• [ ] Findings for devfile/registry-support/index/generator
• [ ] Findings for devfile/registry-support/index/server
• [ ] Findings for devfile/registry-support/tests/integration
• [ ] Findings for devfile/registry-operator
• [ ] Findings for devfile/alizer

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.