feat(task): Add support for enabling task watchdog on an espp::Task

[finger563]

Description

• Add static bool Task::configure_task_watchdog(timeout_ms, panic_on_timeout) to initialize / reconfigure the watchdog timer subsystem.
• Add bool Task::start_watchdog() and bool Task::stop_watchdog() to (de-)register the task with the watchdog timer and inform the task to start resetting the watchdog timer.
• Add static std::string Task::get_watchdog_info(error_code), which can be used (with some caveats mentioned in the docstrings) to get info about tasks which triggered the watchdog.
• Add examples for configuring the watchdog to the task example
• Update task example to use logger for easier to read / clearer delineation between the tests.

Motivation and Context

During debugging, it can be very useful to track execution of various tasks and ensure they do not deadlock or block for too long. This involves using the task watchdog - for which this PR adds convenience functions to configure the watchdog timer system and start/stop the watchdog for a given espp::Task.

How has this been tested?

Building and running task/example on a QtPy ESP32s3.

Screenshots (if appropriate, e.g. schematic, board, console logs, lab pictures):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update
• Hardware (schematic, board, system design) change
• Software change

Checklist:

• My change requires a change to the documentation.
• I have added / updated the documentation related to this change via either README or WIKI

Software

• I have added tests to cover my changes.
• I have updated the .github/workflows/build.yml file to add my new test to the automated cloud build github action.
• All new and existing tests passed.
• My code follows the code style of this project.

[github-actions]

✅Static analysis result - no issues found! ✅