Change behaviour of VGPU_type import lookup

When attempting to import a VGPU_type, look for the equivalent existing
VGPU_type using the (model_name,vendor_name) tuple, rather than
(model_name,framebuffer_size).

This matches the lookup in Xapi_vgpu_type.find_or_create

Signed-off-by: John Else <john.else@citrix.com>
CA-121019: Loosen restrictions on VGPU_type import

When importing a VGPU_type which doesn't exist locally, import the
record instead of failing the import. We'll end up with a VGPU which has
this type, but no PGPUs which support this type, so the VM with the VGPU
will be unable to start.

The VM will be able to start once a PGPU which supports the type is
available.

Signed-off-by: John Else <john.else@citrix.com>
Merge pull request #1576 from johnelse/vgpu-type-import

VGPU_type import fixes