Feature Request: Implement -adt 0 Option in keyble-mqtt for Persistent Connection

[R3ITOSv87]

Issue: The current implementation of keyble-mqtt does not support the -adt 0 option available in keyble-sendcommand. This option allows for a persistent connection to the smart lock, reducing the command execution delay from 5-10 seconds to approximately 1-1.5 seconds.

Steps to Reproduce:

1. Install keyble and keyble-mqtt using the standard installation process.
2. Send a command to the smart lock via keyble-sendcommand --command open.
3. Observe the delay before the smart lock executes the command.

Expected Result: The command is executed with minimal delay.

Actual Result: There is a delay of 5-10 seconds before the command is executed.

Proposed Solution: Implement the -adt 0 option in keyble-mqtt to allow for a persistent connection to the smart lock. This would reduce the command execution delay, improving user experience.

Potential Implications: A persistent connection may prevent other devices from connecting to the smart lock and could potentially increase battery usage. However, the benefits of reduced delay may outweigh these potential downsides for many users.

Request: Please consider adding support for the -adt 0 option in keyble-mqtt.

I would be happy to assist with the implementation if provided with the right approach.