This PR will deal with publish and message handling. Currently it is not possible to set a QoS on the publish messages besides 1; QoS=1 and QoS=0 are both allowed on AWS IoT, so I will pass the QoS as an option for publishes, and allow the TortoiseClient to set a default QoS when otherwise not specified.
[x] Make it possible to pass in options to the tortoise handler, and add options to publish (with defaults), such that the user can specify the qos. If none is set it will use the "default" qos, which can be defined in the tortoise client state, and default to QoS=1
[ ] Update the pending state in the Hare such that we store the options list for the individual messages
This PR will deal with publish and message handling. Currently it is not possible to set a QoS on the publish messages besides 1; QoS=1 and QoS=0 are both allowed on AWS IoT, so I will pass the QoS as an option for publishes, and allow the TortoiseClient to set a default QoS when otherwise not specified.
[x] Make it possible to pass in options to the tortoise handler, and add options to publish (with defaults), such that the user can specify the qos. If none is set it will use the "default" qos, which can be defined in the tortoise client state, and default to QoS=1
[ ] Update the pending state in the Hare such that we store the options list for the individual messages