New Types and Parameter Handling

[Mudrekh]

This is a follow up PR to this #45 .

It tries to address a few issues in generating soap/xml when sending requests to devices by using the same library that parses xml to parse the json from function calls. The revised function fixes two issues:

• Optional parameters that are passed from the calling function are stripped out if they are undefined. Previously, this was an issue because the function could not call Object.keys on the undefined properties. Now, it avoid empty nodes in the request like <tt:ProfileToken/>.
• Parameters passed in that are complete objects can now have attributes that are properly generated. This results in strings like <trt:Configuration token="0">. Attributes are specified just like they are parsed; in a _attributes property. This is important for some functions like Media.SetVideoEndocoderConfiguration which expect the 'token' to be passed as an attribute.

Additionally, it fixes some issues with type definitions by parsing types from the WSDLs. Some of the types used by ONVIF are only defined in the WSDL under schemas and not in the XSDs.

[Mudrekh]

@patrickmichalina I avoided committing the generated files in docs/api to avoid bloat in this PR. It was something like 700+ file changes...

[patrickmichalina]

This is great thanks!

[patrickmichalina]

:tada: This PR is included in version 9.0.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: