No defined behaviour when incorrect arguments are passed to API calls

[kriswest]

Enhancement Request

FDC3 standardizes error strings that are returned by FDC3 API calls. FDC3 2.1 added a number of MalformedContext errors to handle cases where an invalid context object is passed (e.g. an object without a type property). However, there are no standardized errors to provide in response to API calls that have other types of invalid arguments, for example, a a call to addContextListener where a number or boolean is passed as the context type, or handler function.

Create InvalidArguments error types in the ChannelError, OpenError and ResolveError enumerations to handle these cases.