…ifests

Signed-off-by: Joe Lanford <joe.lanford@gmail.com>

Signed-off-by: Jian Zhang <jiazha@redhat.com>

From:
- #320
- #345
- #348
- #347
- #350
- #351
- #355
- #358

NOTE: The commits were squashed but no changes are applied.

Signed-off-by: Todd Short <todd.short@me.com>
(cherry picked from commit c25c411)

…ut format to allow generate xml

…Checks

…uite and small cleanups

Motivation:

When attempting to upgrade argocd-operator from v0.5.0 to v0.7.0, the upgrade process fails during the preflight CRD safety validation. The validation correctly detects that the `argocds.argoproj.io` CRD has been modified between the two versions.

The specific error reported is:

```
CustomResourceDefinition argocds.argoproj.io failed upgrade safety validation. "ChangeValidator" validation failed: version "v1alpha1", field "^.status.applicationController" has unknown change, refusing to determine that change is safe
```

However, changes between the CRD versions in this instance are limited to non-functional updates in the description fields of various properties (e.g., status.applicationController).`ChangeValidator` lacks a specific rule to classify a description-only update as safe, which blocks legitimate and otherwise safe operator upgrades.

Solution:

This PR enhances the CRD upgrade safety validation logic to correctly handle changes to description fields by introducing a new `ChangeValidation` check for `Description`, and registering the check by adding it to the default list of `ChangeValidations` used by `ChangeValidator`.

Result:

Non-functional updates to documentation fields are now deemed safe(which resolves the upgrade failure for argocd-operator from v0.5.0 to v0.7.0)

This is a hack to backport "NetworkPolicy object kind in bundles" support from
operator-framework/operator-registry#1675
The feature was introduced in OCP 4.20 with a operator-registry bump to v1.55.0.
Ref:
1. operator-registry v1.55.0 release: https://github.com/operator-framework/operator-registry/releases/tag/v1.55.0
2. operator-registry bump in OCP 4.20: operator-framework/operator-controller#1981
Because the upstream PR is not being backported in operator-registry to older tags (with new z stream releases),
this achieves a downstream-only backport for this feature.

Adds a Netwok Policy to the end-to-end test bundles and adds a check to
the tests that the Network Policy resources are created.

Signed-off-by: Tayler Geiger <tayler@redhat.com>

…mping deps

OPRUN-4216, OCPBUGS-63405: Port CRD upgrade safety carry from 4.20 without bumping deps