Bug 10108: Copy LoadBalancer config to AgentClusterInstall for BareMetal platform

[mpmprock3]

Summary

This PR fixes issue #10108 where the loadBalancer configuration from install-config.yaml was
not being copied to the AgentClusterInstall manifest during agent ISO creation.

When deploying an OpenShift cluster with platform: baremetal and loadBalancer: type: UserManaged, users should be able to use the same VIP address for both API and Ingress. The
installer correctly validates this configuration and generates the ISO, but the assisted-service
running on the booted node fails validation because it checks the AgentClusterInstall manifest
for the loadBalancer configuration which was missing.

Changes

• Copy LoadBalancer configuration from install-config.yaml to
  AgentClusterInstall.Spec.LoadBalancer for BareMetal platform
• Add convertLoadBalancerType() helper function to convert between
  configv1.PlatformLoadBalancerType and hiveext.LoadBalancerType
• Add unit test for UserManaged LoadBalancer configuration

Testing

• All existing tests pass
• Added new test case: "valid configuration with UserManaged LoadBalancer"
• Manually verified: Generated agent-cluster-install.yaml now includes loadBalancer: type: UserManaged

Fixes: #10108

[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 pawanpinjarkar 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:

• pkg/asset/agent/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]

@mpmprock3: all tests passed!

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.