[C++] Better handling mem* api that behave sanely on NULL input

[mapleFU]

          I think we take a systematic approach to this and make wrappers to `mem*` functions that behave sanely on `NULL` input.

This article [1] discusses the issue in detail and points to approaches taken by projects like boringssl. [2] There is also a proposal from prolific LLVM contributors for fixing this at the C standard level. [3]

[1] https://davidben.net/2024/01/15/empty-slices.html
[2] https://boringssl.googlesource.com/boringssl/+/17cf2cb1d226b0ba2401304242df7ddd3b6f1ff2%5E%21/
[3] https://docs.google.com/document/d/1guH_HgibKrX7t9JfKGfWX2UCPyZOTLsnRfR6UleD1F8/edit?tab=t.0

Originally posted by @felipecrv in #44794 (comment)

[felipecrv]

Make the wrappers inlineable (defined in a header) so the checks can be elided by the compiler when it can be proven at the callsite that the pointer is not null already.

[felipecrv]

Another idea (suggest the wrappers with clang-tidy warnings): #44794 (comment)