Use Conditions from apimachinery, specifically k8s.io/apimachinery/pk…

[joshuatcasey]

Use Conditions from apimachinery, specifically k8s.io/apimachinery/pkg/apis/meta/v1.Conditions

Probably try to merge #1646 and make all required pipeline changes before running this through the pipelines.

Release note:

This includes a small breaking change for consumers of the generated client code.

If consumers directly import one of the removed `Conditions` structs, they will need to import the `Condition` struct from the `k8s.io/apimachinery/pkg/apis/meta/v1` library.

[codecov]

Codecov Report

Merging #1644 (64f1bff) into main (96fcfe4) will increase coverage by 0.01%.
The diff coverage is 90.90%.

@@            Coverage Diff             @@
##             main    #1644      +/-   ##
==========================================
+ Coverage   75.53%   75.55%   +0.01%     
==========================================
  Files         166      166              
  Lines       15159    15159              
==========================================
+ Hits        11451    11454       +3     
+ Misses       3406     3404       -2     
+ Partials      302      301       -1     

Files Changed	Coverage Δ
...sorconfig/oidcclientwatcher/oidc_client_watcher.go	87.65% <ø> (ø)
internal/testutil/oidcclient.go	0.00% <ø> (ø)
...onfig/ldapupstreamwatcher/ldap_upstream_watcher.go	75.86% <66.66%> (ø)
...streamwatcher/active_directory_upstream_watcher.go	90.07% <88.88%> (ø)
...onfig/oidcupstreamwatcher/oidc_upstream_watcher.go	95.06% <93.75%> (ø)

... and 2 files with indirect coverage changes

[cfryanr]

LGTM but can we hold this back until we merge #1419 due to the expected merge conflicts?

[cfryanr]

I looked at what the merge conflicts would be in detail by running a trial merge and they aren't that bad, so I think we can go ahead and merge this now. I rebased main into the PR branch and will mark it for auto-merge.