Update to operator-sdk 1.23

[cpmeadors]

We are currently on operator-sdk 1.20. Latest is 1.23. We need to update the operator-sdk version and apply all the migration changes listed in the docs:

https://sdk.operatorframework.io/docs/upgrading-sdk-version/v1.21.0/
https://sdk.operatorframework.io/docs/upgrading-sdk-version/v1.22.0/
https://sdk.operatorframework.io/docs/upgrading-sdk-version/v1.23.0/

This will also need a golang update to 1.18. Not sure if that can be a separate change or not, but I will file a separate issue for tracking.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[littlejawa]

Making progress on this: moved to 1.21 (#233) and 1.22 (#235).
Working on 1.23

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[littlejawa]

Actually, this was fixed with #237
We can close this (I can't do it myself though :-/ )

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.