Description of problem:
When building a VM on a VMware compute resource with a NSX logical network we get the following traceback:

Could not find virtual machine network interface matching 000-mindy-smack.example.org

When applying the following patch from upstream:

https://github.com/fog/fog-vsphere/commit/055fb8c7a6679780f3856516c74515580a043231

We get wrong number of arguments (given 2, expected 1)

I did a remote session with the customer and looked in the database and it appears satellite/fog-vsphere is not familiar with NSX networks.

We can see that it finds a network and treats it as a standard portgroup:

interfaces=>[ <Fog::Vsphere::Compute::Interface
mac=nil,
network="network-o2246621",
name="Network adapter",
status=nil,
connected=nil,
summary="VM Network",
type=RbVmomi::VIM::VirtualVmxnet3,
key=nil,
virtualswitch=nil,
server_id=nil
>]

But we should have some additional network parameters for NSX.

When we have a network that is on a distributed switch we see it as the following:

networkname(distributed switch)

This customers network was in there as a standard switch which just shows up as `networkname`

Version-Release number of selected component (if applicable):

Satellite 6.7
vSphere 6.7
NSX v4

How reproducible:

Steps to Reproduce:
1. Install Satellite 6.7
2. Connect vCenter that has NSX installed as compute resource
3. Try to build a VM

Actual results:
Could not find virtual machine network interface matching 000-mindy-smack.example.org

Expected results:

VM to build correctly