feat(event_manager): Allow fully configuring subscriber task

[finger563]

Description

• Add API to support providing a full Task::BaseConfig when registering a subscriber, so that you can optionally specify name, stack size, priority, and pinned core id
• Update event manager example to use new API
• Update task to have libfmt printing helpers for task config and base config.

Motivation and Context

Prior to this PR, you could only (optionally) set the stack size for a subscriber task, but could not set the priority or the core id for the task. This would mean you could not for instance set higher priority to higher priority event subscribers and you could not pin them to a specific core for resource management. Additionally, you could not name the task whatever you liked.

How has this been tested?

Building and running the event manager example

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! ✅