[Feature] different log levels and tag modules

[stefan123t]

I would like to limit the amount of information that is logged via both Serial Console and Web Console to allow debugging some long term issues in specific components / modules of the code.

Currently I am drowning in the messages send via Hoymiles.cpp and HoymilesRadio.cpp on Commands being sent and Packets being handled. At least the latter I would like to mute as I am trying to focus on other modules / components of the OpenDTU, e.g. lost WiFi connection, etc.

IMO it would make sense to use a logging framework, e.g. ESP-IDF which allows for several Log Levels (Error, Warning, Info, Debug, Verbose) as well as allows tagging individual modules (e.g. Hoymiles, HoymilesRadio, etc.)

Logging library
https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-reference/system/log.html

In each C file that uses logging functionality, define the TAG variable as shown below:

static const char* TAG = "MyModule";

Then use one of logging macros to produce output, e.g:

ESP_LOGW(TAG, "Baud rate error %.1f%%. Requested: %d baud, actual: %d baud", error * 100, baud_req, baud_real);

...

To configure logging output per module at runtime, add calls to the function esp_log_level_set() as follows:

esp_log_level_set("*", ESP_LOG_ERROR);        // set all components to ERROR level
esp_log_level_set("wifi", ESP_LOG_WARN);      // enable WARN logs from WiFi stack
esp_log_level_set("dhcpc", ESP_LOG_INFO);     // enable INFO logs from DHCP client