Add support for multiple nics with vmware cloud director in the UI

[4ch3los]

What this PR does / why we need it:
This PR completes the feature of multiple nics for vmware cloud director workers(introduced in kubermatic/machine-controller#1941 & kubermatic/operating-system-manager#471 ). By Allowing to define additional networks, which will also be added to the machinedeployment

Which issue(s) this PR fixes:

What type of PR is this?
/kind feature

Special notes for your reviewer:
This PR depends on kubermatic/machine-controller#1941 & kubermatic/operating-system-manager#471

Does this PR introduce a user-facing change? Then add your Release Note here:

You can now define multiple Networks for nodes of your vmware cloud director machinedeployment

Documentation:

NONE

[kubermatic-bot]

[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 waseem826 for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• modules/api/pkg/OWNERS
• modules/api/pkg/api/OWNERS
• modules/web/OWNERS
• modules/web/src/OWNERS

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

[kubermatic-bot]

Hi @4ch3los. Thanks for your PR.

I'm waiting for a kubermatic member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.