vmware.vmware.import_content_library_ovf needs ability to import vm straight from vcenter into content library ovf

##### SUMMARY

This module or maybe one similar needs the ability to similar to how its performed in vcenter.

I tried src: "ds://" to the path of the vm and just got an error

Failed to complete upload of OVF to vCenter: {messages :
[LocalizableMessage(id='vapi.bindings.method.impl.unexpected',
default_message='Provider method implementation threw unexpected exception:
com.vmware.vapi.std.errors.InternalServerError',
args=['com.vmware.vapi.std.errors.InternalServerError'], params=None,
localized=None)], data : None, error_type : INTERNAL_SERVER_ERROR}
##### ISSUE TYPE
- Feature Idea
Straight clone vm into Content Library as OVF.
##### COMPONENT NAME

vmware.vmware.import_content_library_ovf
##### ADDITIONAL INFORMATION

```yaml
Right click on vm ->clone-> Clone as Template to library-> Template Type OVF.. This does a straight conversion to from vcenter VM to Content Library OVF.
```

Start with the vmware.vmware.import_content_library_ovf module and compare its current OVF upload behavior with the vCenter workflow described in the issue. Investigate how a VM can be cloned directly into a Content Library as an OVF, including the reported ds:// source error. Done means the module supports that workflow with documented usage and coverage for the new behavior.

Written by the indexing model from the issue text.