feat: include reason for low security in "node added" parameter

[AlCalzone]

For users it is currently pretty opaque why a node was not added with Security S0/S2. With this PR, we surface a multitude of reasons as part of the "node added" event, so applications can give some more details on why the secure inclusion failed.

The InclusionResult contained in the 2nd event parameter

// "node added"
(node: ZWaveNode, result: InclusionResult) => void

now has a property lowSecurityReason when lowSecurity is true. This is an enum value with the following possibilities:

enum SecurityBootstrapFailure {
	/** Security bootstrapping was canceled by the user */
	UserCanceled,
	/** The required security keys were not configured in the driver */
	NoKeysConfigured,
	/** No Security S2 user callbacks (or provisioning info) were provided to grant security classes and/or validate the DSK. */
	S2NoUserCallbacks,
	/** An expected message was not received within the corresponding timeout */
	Timeout,
	/** There was no possible match in encryption parameters between the controller and the node */
	ParameterMismatch,
	/** Security bootstrapping was canceled by the included node */
	NodeCanceled,
	/** The PIN was incorrect, so the included node could not decode the key exchange commands */
	S2IncorrectPIN,
	/** There was a mismatch in security keys between the controller and the node */
	S2WrongSecurityLevel,
	/** Some other unspecified error happened */
	Unknown,
}

fixes: #3233

[AlCalzone]

@zwave-js-bot automerge