Fix #1344, UT assert stub return values

[jphickey]

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
Improves default support for return values of sizes other than 32 bits. Previously this required a custom handler for any value that was not a 32 bit integer. With this update any integer value can be used, and a value translation will occur if the size is different. Thus boolean values, 8,16, and 64-bit ints can be configured through the same basic API without needing to add a handler.
Fixes #1344

Testing performed
Build and run all tests, including CFS app tests, to confirm all still run as expected.

Expected behavior changes
No change to existing behavior - all currently-implemented test cases should continue to behave as they have in the past, whether they used a 32-bit integer return or if they had a custom hook/handler.

Going forward, it should no longer be required to implement a custom handler for the sole purpose of adjusting the size of the return value in case it is not a 32-bit integer. As a fallback default, any return value that is unset by a test will be memset to 0. So a pointer stub return will get NULL, a boolean will get FALSE, and any numeric value of any time will be zero.

The UT_SetDeferredRetcode and UT_SetDefaultReturnValue functions now accept a UT_IntReturn_t value instead of int32. This typedef is defined using the C99 ptrdiff_t type, which will be 64 bits in size on modern hardware. When passing by value from an int32, this should be transparent, but it is large enough to also allow test cases to pass in pointer values here without truncating.

System(s) tested on
Debian

Additional context
API to set return values is still numeric in nature. This adds some framework to allow fully-typed values and abstract objects bigger than ptrdiff_t values to be returned, but there is no API yet - that can be added in a future change.

Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

[dzbaker]

CCB 19 January 2023: Will review after next release.