Provide HA values for capm3-virt as component

What does this MR do and why?

The proposition here is keep capm3 mono-node configuration as example (reverting from !2384 (merged)) and have HA (= multi-node) configuration as option (= kustomize component).

This change is motivated by the fact that mono-node config is still useful for test deployment (in dev env by example) and maybe reintroduced in CI pipeline for quick and cheap testing. It is easier to patch a mono-noce env values to set multi-nodes env than to do the reverse.