Handle 'strerror_r' idiosyncrasies in the platform layer

[elfenpiff]

Brief feature description

The function strerror which is used in the posixCall is not thread-safe, see man strerror attribute section. This can lead to undefined behavior, race condition and fatal crashes when the posixCall is used concurrently - which is a standard use case in iceoryx - and a underlying call fails.

There are strerror_r and strerror_s as thread-safe alternatives and iceoryx already switched to strerror_r. There are some idiosyncrasies in strerror_r like different return types, char* vs int, and other stuff. Furthermore on Windows only strerror_s is available which is not source compatible but offers the same functionality as one of the strerror_r versions.

All of this should be handled in the platform layer instead of the posixCall

Extracted from: #1196