Fix #1193, Change format of UtAssert_StringBufCompare

[thnkslprpt]

Checklist

• I reviewed the Contributing Guide.
• I signed and emailed the appropriate Contributor License Agreement to GSFC-SoftwareRelease@mail.nasa.gov and copied cfs-program@lists.nasa.gov.

Describe the contribution

• Fixes UtAssert_StringBufCompare output of strings could be put on top of each other for easier problem identification #1193
  • Comparison strings are now formatted one above the other and aligned to make identifying the discrepancy easier.

An example:

Testing performed
GitHub CI actions and local cFS test suite run all passing successfully.

Expected behavior changes
The change makes it easier to identify the discrepancy between the strings in case of a failed test.

Only slight downside is the increase in length of the test log... (each call to UtAssert_StringBufCompare() now results in 3 lines printed instead of 1).
There are currently ~40 uses of UtAssert_StringBufCompare() in cFE and OSAL.

Contributor Info
Avi Weiss @thnkslprpt

[github-advanced-security]

You have successfully added a new CppCheck configuration cppcheck. As part of the setup process, we have scanned this repository and found no existing alerts. In the future, you will see all code scanning alerts on the repository Security tab.

[github-advanced-security]

You have successfully added a new CodeQL-coding-standard configuration coding-standard. As part of the setup process, we have scanned this repository and found 785 existing alerts. Please check the repository Security tab to see all alerts.

[github-advanced-security]

You have successfully added a new CodeQL-security configuration security. As part of the setup process, we have scanned this repository and found 4 existing alerts. Please check the repository Security tab to see all alerts.