…cros

These new warnings are detected by the new compiler. They are all places
in unit test where an uninitialized value is passed via "const" pointer
into a unit under test.  By definition a "const" pointer is always an
input.

While the warning is pedantically true - should not pass an uninitialized
struct as an input - these were all unit tests where the object value
is a don't-care value, so it does not matter.  But to fix the warning,
simply need to initialize a value before making the call.

- Refactors symbol table searching to include
  both local and global symbol tables for POSIX
- Renamed global search to generic since there
  isn't currently a use case for global only search

Fix #1204, Search global and local symbol tables #1206

…ert_STUB_COUNT

Fix #1200, Add missing space to UtAssert_STUB_COUNT

…uivalents-for-UtAssert_UINT32-macros

Fix #1196, Add UINT8 and UINT16 equivalents for UtAssert_UINT32_<Comparison> macros

Fix #1199, correct warnings on gcc11

 # Please enter a commit message to explain why this merge is necessary,

Fix #1210, Set output in OS_stat handler

Fix #1188, Reuse CodeQL, Static Analysis, Format Check