Initial support for reading the internal temperature probe (second attempt 😅)

[k8ieone]

Same as #77 except without the rouge file.

[bartowl]

This PR is really interestiung. Sadly if a device does not report TemSen by default, this PR causes the process to crash:

0|HVAC_0  | [MQTT] Connected to broker
0|HVAC_0  | [UDP] Connected to device at 192.168.2.10
0|HVAC_0  | [UDP] New device registered: 1edd6ca6
0|HVAC_0  | [UDP] Device 1edd6ca6 is bound!
0|HVAC_0  | TypeError: Cannot read properties of undefined (reading 'toString')
0|HVAC_0  |     at Object.onStatus (/usr/src/app/index.js:77:145)
0|HVAC_0  |     at Device._handleResponse (/usr/src/app/app/deviceFactory.js:171:20)
0|HVAC_0  |     at Socket.<anonymous> (/usr/src/app/app/deviceFactory.js:45:47)
0|HVAC_0  |     at Socket.emit (node:events:527:28)
0|HVAC_0  |     at UDP.onMessage [as onmessage] (node:dgram:922:8)

On those devices one needs to explicitely ASK for TemSen to get the readout, so this should be implemented rather in a way, if TemSen is not included, then ask for it interactively and publish only when received...
See: https://github.com/tomikaa87/gree-remote#getting-the-current-temperature-reading-from-the-internal-sensor

[k8ieone]

Ouch, I was wondering what would happen on a device that doesn't report it. Now I know 😅

Honestly tho, I'm not a JS developer by a long shot and my "solution" is hacky and as your teating reveals, unfinished.

If anyone's interested in doing this a different/better way, please feel free to do so. I don't have much time on my hands at the moment.