fix(monitor): properly display no core affinity as -1

[finger563]

Description

• Fixed bug in task monitor which returned core_id natively, meaning that tskNO_AFFINITY would be returned as a very large number instead of -1. Now it checks that value specifically and converts it to -1 for simpler display
• Simplified cdoe for returning task info since both cases were doing the same thing

Motivation and Context

Seeing core id in task info printing is helpful for determining processor utilization. A small number (-1) for no core affinity is easier to visually parse than a very large number and is more consistent with the APIs for setting core affinity.

How has this been tested?

Building and running to print task info.

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

Example:

Types of changes

• [x] 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
• [x] 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.
• [x] All new and existing tests passed.
• [x] My code follows the code style of this project.

[github-actions[bot]]

:white_check_mark:Static analysis result - no issues found! :white_check_mark: