Bump to Go 1.19, Ginkgo v2 & kubebuilder 3.7.1

[laxmikantbpandhare]

Description of the change:
Changes in this PR are:

• Modified go version to 1.19 in all the places and Kubebuilder to k8s 1.25
• The config-gen is completely removed from Kubebuilder. As part of this bump, the website content of SDK was updated where the doc is referring to config-gen.
• Updated ginkgo to ginkgo/v2 in all of the files. The reason behind it is that Kubebuilder updated to ginkgo/v2.
• Updated all the io/ioutil imported packages to either io or os. io/ioutil got deprecated in 1.16 and no longer it is used. Updated all the files in SDK.
• Ansible scaffolding got modified in order to incorporate with Kubebuilder --component-config flag changes. Previously, it was scaffolding and doing some file changes without considering the --component-config flag.
• This PR bumped Kubebuilder to a newer version and it got the recent PR changes for the --component-config flag.
• Helm scaffolding got modified in order to incorporate with Kubebuilder --component-config flag changes. Previously, it was scaffolding and doing some file changes without considering the --component-config flag.

Motivation for the change:

• Ginkgo version mismatch in Kubebuilder and operator-sdk. ginkgo updated to ginkgo/v2
• Updated io/ioutil to io or oc as io/ioutil got deprecated in 1.16
• Updated go version to 1.19

Checklist

If the pull request includes user-facing changes, extra documentation is required:

• Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
• Add or update relevant sections of the docs website in website/content/en/docs

[laxmikantbpandhare]

Updated the Kubebuilder version as the new KB version has ginkgo/v2 changes.

[laxmikantbpandhare]

/hold

[jmrodri]

/hold

I'm still reviewing the latest changes.

[varshaprasad96]

@laxmikantbpandhare great work! Thanks for handling this big chunk of updates. Just a few changes in changeling fragments - It would be nice to include a snippet of git diff in migration sections, so that its easier for users to know what is getting added and/or deleted. Rest of the changes in SDK and plugins look good!

[jmrodri]

The changelog is meant to convey what things have changed that would affect a user's project. They don't care about changes we made to internal code.

How will go 1.19 update impact a users project? the io/ioutil is a good example.

How will ginkgo v2 affect them? They dont' care that we had to rename an internal variable like LabelsMap. They care that they might have to change their suite_test.go. So look at the difference of the testdata changes. THAT is usually what they care to see. So if the testdata changes the Makefile, what changed? That is what they will want to see.

Also, migrations are only important if it affects the scaffolded out project. If the change has no effect then no need for a migration.

I know it's not easy but you'll want to think about each of these as you write the changelogs. Usually the changelogs are easy because the changes in the PR aren't that big. But this is a HUGE PR and a lot changed :)

[jmrodri]

/hold cancel

I finished my review

[everettraven]

/lgtm