Fix #2592, Yield cpu to other tasks in SB Perf Test

[pepepr08]

Depends on #2591 and #2996

Checklist (Please check before submitting)

• I reviewed the Contributing Guide.
• I signed and emailed the appropriate Contributor License Agreement to [email protected] and copied [email protected].

Describe the contribution

• Fixes Functional tests get stuck at SB Performance test #2592 Greatly increase timeout on SB Perf test to give command tasks enough time to finish before exiting the telemetry receiver task.
• Fix a typo in Telemetry task name

Testing performed
Steps taken to test the contribution:

1. Ran functional test using RTEMS on MUSTANG processor card

Expected behavior changes
SB performance tests runs to completion

System(s) tested on

• Hardware: MUSTANG Proc card
• OS: RTEMS 5
• Versions: latest on main as of today

Additional context
Add any other context about the contribution here.

Third party code
If included, identify any third party code and provide text file of license

Contributor Info - All information REQUIRED for consideration of pull request
Jose F Martinez Pedraza / GSFC 582

[pepepr08]

Updated code to use new strategy. We now yield the cpu to the other task by doing a OS_TaskDelay(0). This slows downs the total messages per second sent, but solves the issue where one transmit task hogs the cpu causing the other task to timeout and exit.

Results when running on MUSTANG Processor card:
2 Tasks SB Perf Test:
Without task yield: sb_performance_test.c:348 - Message Rate: 2242.8 messages/sec
With task yield: sb_performance_test.c:354 - Message Rate: 1911.1 messages/sec
with task yield(1000):sb_performance_test.c:365 - Message Rate: 2116.5 messages/sec

4 Tasks SB Perf Test:
Without task yield: sb_performance_test.c:578 - Message Rate: 1293.2 messages/sec
With task yield: sb_performance_test.c:578 - Message Rate: 1225.2 messages/sec
with task yield(1000): sb_performance_test.c:597 - Message Rate: 1255.7 messages/sec