Allow enable/disable CM in App mode and disconnect/reconnect on failed commands

[iranl]

• CM
  According to the API Continuous mode can only be disabled/enabled when paired as a Bridge using the LockAction.
  When paired as app CM can still be enabled/disabled using the separate command available for this (0x0057), although this does require a valid PIN to be set.

• Disconnect on failed commands
  NUKI_ALT_CONNECT mode tries to reuse connections as much as possible. This can lead to stuck connections in some cases. This PR disconnects (and reconnects) when commands fail instead of trying to reuse the failing connection (when NUKI_ALT_CONNECT is defined).

[technyon]

"Disconnect on failed commands" seems a very good idea. Shouldn't we just make it the default bahavior and remove the #ifdef ?

[technyon]

Did you check if CM is a problem like this in bridge mode? I had paired and bridge mode and never had a problem settting CM. Maybe it's not enforced as of now, but sticking to the API is a good thing anyway.

[iranl]

API only says this is only not allowed in App mode. So this PR also only changes this behaviour when not in Bridge mode.

Disconnect on failed is mainly an issue in the alt connect mode, which leans more heavily on trying to reuse connections.

Changes (and alt connect mode) could be made default if no issues arise when used for a while in NukiHub.

[technyon]

Lets enable alternative mode for the upcoming test. Please remove the cast to int as suggested, then we can merge.

[iranl]

Cast to int has been removed.

Alt connect mode has been enabled in NukiHub for a couple of months.