Post-process HTTPProxy CRD schema to remove error as a required field

[tsaarni]

This PR adds a post-processing step to make generate to prevent status.loadBalancer.ingress[].ports[].error from being incorrectly marked as required in the HTTPProxy CRD schema, which caused load balancer status update failures.

The issue happens because the HTTPProxy embeds the Kubernetes core_v1.LoadBalancerStatus. This type contains PortStatus struct with some conflicting markers, and controller-tools v0.16.x changed how it handles conflicting +optional and +kubebuilder:validation:Required marker. Rewriting the status struct to remove its dependency on the external package would be best solution, but it would break Go API compatibility for HTTPProxy.

The modification uses kubectl patch with the exact path to the data structure and includes test for recognizing if the field is still there before processing. This approach should be robust and not affect wrong fields.

Fixes #7391

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.85%. Comparing base (3fcf197) to head (986a537).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7408   +/-   ##
=======================================
  Coverage   81.85%   81.85%           
=======================================
  Files         130      130           
  Lines       15766    15766           
=======================================
  Hits        12906    12906           
  Misses       2576     2576           
  Partials      284      284           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.