Vrpc

Fixed

- Possible exception when using deprecated form of `VrpcRemote::getInstance`
[NodeJS]

Fixed

- Spuriously occurring RPC timeouts on calls that actually successfully
travelled the network by removing the promise-based waiting from all mqtt
pub/sub calls. Turns out that those callbacks may come later then event
RPC answer! [NodeJS]

Added

- Option `noWait` on `VrpcRemote::getInstance` skipping any waiting for the
instance to appear if not currently found in the local cache. [NodeJS]

Changed

- `VrpcRemote::getInstance` will try first locally, second remotely to find
the instance (exception is thrown after timeout) [NodeJS]

Fixed

- VrpcAgent: unregistration of named instances [NodeJS]
- VrpcAgent: ordering of classInfo message w.r.t. named creation [NodeJS]

Changed

- handling of agent answer implementation (always using single promise) [NodeJS]
- improved error message on timed out functions [NodeJS]
- triggering a deprecation notice upon calling `VrpcRemote::connected()` [NodeJS]
- naming of info messages:
- `__agentInfo__`
- `__classInfo__`
- `__clientInfo__`

Removed

- implicit triggering of MQTT connection within VrpcRemote constructor [NodeJS]
- waiting for retained info messages during connect [NodeJS]

Added

- explicit `VrpcRemote::connect()` function, performing the MQTT connect [NodeJS]
- 'error' and 'connect' event for `VrpcRemote` [NodeJS]

Fixed

- ambiguity between classInfo and clientInfo message subscription
- documentation

Changed

- got rid of the requirement to await twice for asynchronous agent functions
[NodeJS]

Added

- two events on VrpcRemote: `instanceNew` and `instanceGone` [NodeJS]

Changed

- API for `VrpcRemote::getInstance` and `VrpcRemote::delete` [NodeJS]
- provisioning of instanceId only is acceptable now, explicit context is
optional.
- old API usage is still supported, but generates a deprecation report
- automatic schema validation now injects schema defaults [NodeJS]

Fixed

- missing topic un-subscription after client death [NodeJS]