Added device_class for sensors published to Home Assistant

[paulhomes]

Adds the device_class attribute to sensors published to Home Assistant so they can be charted alongside other entities of a similar type - see issue #470

[davidusb-geek]

@paulhomes Just pushed a fix for unit testing

[paulhomes]

This branch has been working for me, and I think is potentially ready to merge, but there are a few places where I have specifically not added any handling for device_class as they are not actions that I have used as yet and am unsure if device_class is needed or wanted in those locations. More specifically:

1. In command_line.py I haven't added a model_predict_device_class in the forecast_model_predict() function around line 801 nor a mlr_predict_device_class in the regressor_model_predict function around line 988 and likewise added no equivalent handling of a potential model_predict_device_class in the utils.py treat_runtimeparams() function around line 659 nor mlr_predict_device_class around line 680
2. In the retrieve_hass.py post_data() function I have not added device_class in the handling of type_var == "optim_status" around line 602 and type_var == "mlregressor" around line 610

In reviewing this PR for potential merging please could you take a quick look at those and advise on whether you think device_class is warranted in those places (or should be left for another time).

Thanks

[davidusb-geek]

Thanks for pointing out all those cases, yes they need to be considered.
Also there are a bunch of additions to utils.py for this. It's almost done, I will push and probably merge when finsihed

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud