OSASINFRA-4401: Add max_allowed_address_pairs cloud network config e2e test

[danchild]

The cloud-network-config-controller supports an optional max_allowed_address_pairs
field passed via a ConfigMap. The following E2E test provides coverage for two paths:

1. Normal lifecycle where setting the field changes operator behavior and triggers a CNCC deployment
   rollout
2. Degradation path where an invalid value causes the network operator
   to report Degraded with the config key in the message.

The egress-ipconfig annotation parsing logic is abstracted into a separate function to
cover multiple call sites across the openstack-test suite.

Summary of Changes:

• Lift ifAddr, capacity, and NodeEgressIPConfiguration out of
  getEgressNetworkInfo's function body into package-level types
• Extract a parseEgressIPAnnotation helper that handles annotation lookup and
  JSON unmarshalling, calling it in getEgressNetworkInfo and
  getEgressIPCapacityFromNode
• Add BeforeEach setup that records baseline egress IP capacity per node and
  verifies CNCC is healthy before each spec
• Add helper functions for creating/deleting the ConfigMap, waiting for a CNCC
  rollout, checking network operator degraded status, and waiting for recovery
• Valid-value test: set a valid value, verify per-node egress IP capacity reflects
  the configured limit, delete the ConfigMap, and verify capacity returns to baseline
• Invalid-value degradation test: for each of "0", "-5", and "abc", verify
  the network operator enters Degraded state with the config key referenced in the
  message and recover after the ConfigMap is deleted

Dependencies:
openshift/cluster-network-operator#3058
openshift/cloud-network-config-controller#230

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign eurijon for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@danchild: This pull request references OSASINFRA-4401 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

TODO

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@danchild: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/test	1741c5e	link	true	/test test

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.