[zigate-adapter] Improved stability and functionality

[G1K]

Most importantly, the command sending has been improved. The work is not yet 100% complete, but what has turned out is already much better and more stable. And let's solve #285 #252.

Unfortunately, I ran into some difficulties that I described here #252 (comment)
The worst thing is that in the latest firmware when communicating with devices, APDU instances always ended fairecasoimeme/ZiGate#348 and further communication was impossible. As a result, mating did not go through to the end.

Now it seems that there are commits fixing this, but I could not verify that the resulting firmware did not work on my module and the code before the change is completely identical to that in the basic example and works successfully.

Therefore, it was decided to try a clean example from NXP and move the edits a little to support raw messages and LQI. The test results show a more stable firmware version. It lacks a lot in comparison with ZiGATE, and the default settings are designed for a network of 10-20 devices, but the advantages that we managed to get.

• APDUs do not leak
• GP is supported (but so far it has been commented out if you use ZIGate firmware without .. join permit fails)
• Some messages that did not reach the uart, but were received when sniffed
• Group messages are sent via raw (maybe it is also related to 1 problem)
• The firmware is built together with GP and debug messages, in this combination ZIGate does not start on my module

Therefore, I recommend installing this firmware
https://github.com/openlumi/JN-ZigbeeNodeControlBridge-firmware/releases/latest

#242

[Koenkk]

Thanks!