Perform S2 inclusion with DSK verification in Z-Wave JS and correctly handle a DSK timeout or mismatch

Steps

1. Call driver.controller.beginInclusion with strategy: InclusionStrategy.Default and userCallbacks for grantSecurityClasses, validateDSKAndEnterPIN, and abort
2. On grantSecurityClasses, show the requested security classes and resolve with the user's choice within 240 seconds or the process aborts
3. On validateDSKAndEnterPIN, show the partial DSK for comparison and collect the device's 5-digit PIN within 240 seconds
4. If the DSK isn't confirmed or the PIN isn't entered in time, let it time out — Z-Wave JS aborts inclusion and calls abort(); do not retry with S0, since S0 cannot be attempted after S2 has already been tried
5. If S0-only inclusion is genuinely needed (e.g. a lock claiming S2 support that doesn't respond to key exchange), select that as its own explicit inclusion strategy up front, not as a fallback
6. After inclusion, check the "node added" event's result.lowSecurity and result.lowSecurityReason (e.g. Timeout, S2IncorrectPIN, UserCanceled, S2WrongSecurityLevel, S0Downgrade) and warn the user accordingly