test(daemon): assert NetworkUpgradeExecute GVR group matches installe…

[radkomih]

Description

This pull request changes the following:

• Add a require_cluster integration test (TestWithCluster_UpgradeMonitor_GVRMatchesInstalledCRD) that asserts the monitor's NetworkUpgradeExecute GVR (group, resource, served version) matches the CRD solo-operator actually installs. The CRD is looked up by plural name, so a wrong group still resolves the installed CRD and the assertion fails — catching real API-group drift rather than silently skipping.
• Export consensus.NetworkUpgradeExecuteGVR() so the test asserts against the production GVR value instead of a copy.
• Enable SoloOperator in Test_ClusterSetup so its CRDs are provisioned in Phase 2, making the guard a real assertion (not a skip) in Phase 3.
• Refresh the solo-operator CRD lists in the cluster health check (step_health.go) and UAT task (uat.yaml) to the 0.3.2 set (drop networkoperations, add the networkgeneses/networkupgrade* CRDs).
• Bump solo-operator 0.3.1 → 0.3.2 in the infrastructure catalog (with checksum) and update the config integration-test expectation.

Related Issues

• Closes Add integration test asserting GVR group matches installed CRD #851

Manual UAT

[swirlds-automation]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.