MetalLB operator cannot ship in 4.13.z until a CSV issues is fixed.  Currently blocking 4.13.3 for next week.

See https://issues.redhat.com/browse/CVP-3772

ose-metallb-operator-bundle-container-v4.13.0.202306061844.p0.gfde8dc5.assembly.stream-1 failed {*}Operator Bundle Data Linting TestPlease see more details here: http://external-ci-coldstorage.datahub.redhat.com/cvp/cvp-redhat-operator-bundle-image-validation-test/ose-metallb-operator-bundle-container-v4.13.0.202306061844.p0.gfde8dc5.assembly.stream-1/86b65c0a-897d-498c-8dd4-e866e2314c71/cvp-test-report.htmland here: http://external-ci-coldstorage.datahub.redhat.com/cvp/cvp-redhat-operator-bundle-image-validation-test/ose-metallb-operator-bundle-container-v4.13.0.202306061844.p0.gfde8dc5.assembly.stream-1/86b65c0a-897d-498c-8dd4-e866e2314c71/operator-metadata-linting-bundle-image-output.txtthe error is:

Error: Value manager-account: invalid service account found in bundle. This service account manager-account in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV.
Error: Value manager-account: error validating object: metadata.namespace: Forbidden: not allowed on this type. &{map[apiVersion:v1 kind:ServiceAccount metadata:map[creationTimestamp:<nil> name:manager-account namespace:metallb-system]]} 

always