Update go projects to v1.19

[michael-valdron]

/kind user-story
/kind epic

Which area this user story is related to?

/area api
/area library
/area registry
/area alizer

User Story

As a developer of devfile, I want to provide effective patching support the user base of devfile services, so that users continue to devfile services knowing that they have the assurance that these services are receiving the security and bugfix patches when they are needed.

Part of meeting this goal is providing the patches shipped from dependencies of devfile services. With the version of Go used by most of devfile services 1.18 being EOL for some time it is becoming more difficult to provide patches from all the dependencies.

Acceptance Criteria

• Update Devfile API to use Go 1.19
• Update Devfile Registry Operator to use Go 1.19 (Updates for operator sdk v1.28 registry-operator#45)
• Update Devfile Library to use Go 1.19 #1470
• Update Devfile Registry Support Services to use Go 1.19 #1469
• Update Community Devfile Registry to use Go 1.19 #1473
• Update Alizer to use Go 1.19 (Update go version redhat-developer/alizer#182)
• Update Integration Test to use Go 1.19 #1249

[michael-valdron]

We need to include patching dependencies as one of the tasks to do for each of the acceptance criteria items, to address issues such as #1180.

[michael-valdron]

Before starting any child item, we need to ensure consumers of those modules are compatible with Go 1.19 (i.e. using >= 1.19).

[michael-valdron]

Before starting any child item, we need to ensure consumers of those modules are compatible with Go 1.19 (i.e. using >= 1.19).

Some modules may not need this prerequisite, the registry index server for example would not however the devfile library and registry library would need to be compatible with consumer tools and services.

[thepetk]

I've added some commits to update the integration-tests repo to go 1.19 here: devfile/integration-tests#99