Try deleting -Werror in config scripts

[MichalStrehovsky]

No description provided.

[MichalStrehovsky]

/azp run CoreCLR GCC Product Build Linux x64 checked

[azure-pipelines]

No pipelines are associated with this pull request.

[MichalStrehovsky]

No pipelines are associated with this pull request.

Gee thanks for nothing azure-pipelines

[MichalStrehovsky]

Cool so this still doesn't trigger the GCC leg that was seen as failing in #58744.

[MichalStrehovsky]

Before I close this and seriously consider woodworking as a future career development direction, @dotnet/ncl there's a mildly interesting failure in the WASM legs - because we enable -Werror for CMake's configure checks (on the line that I'm deleting in this pull request), our check for HAVE_SYS_POLL_H always fails on MUSL-based targets - not because there's no poll.h, but because MUSL suggests us to #include <poll.h> instead, like POSIX says and issues a warning (causing us to go the !HAVE_SYS_POLL_H paths instead, because of treating the suggestion as error). Not sure if this has any material impact on the product on MUSL-based targets.

(I do wonder how many other CMake configure checks only fail because there is a warning.)

[MichalStrehovsky]

Using pthread_condattr_setclock is tracked in #58737. Closing.