Enable OSSF compiler hardening flags by default

[garazdawi]

This PR enables some extra gcc/clang flags by default that disallow certain types of bugs/attack vectors. From what I can tell the flags do not impact performance, but depending on the usecase they might.

The flags are taken from https://github.com/ossf/wg-best-practices-os-developers/blob/main/docs/Compiler-Hardening-Guides/Compiler-Options-Hardening-Guide-for-C-and-C++.md#-fno-strict-overflow

[github-actions]

CT Test Results

   11 files    253 suites   3h 23m 19s ⏱️
3 240 tests 3 103 ✅ 137 💤 0 ❌
4 709 runs  4 312 ✅ 397 💤 0 ❌

Results for commit 9c916ab.

♻️ This comment has been updated with latest results.

To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass.

See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally.

Artifacts

• Complete CT logs (Download Logs)
• HTML Documentation (Download HTML Docs)
• Windows Installer

// Erlang/OTP Github Action Bot

[garazdawi]

I've come to the realization that if we want to be able to enable these flags by default, we need to force usage of $(CC) as the linker, and not use $(CC) in some places and ld in other. This because the flags passed to the two are very different and we cannot use the builtin AC_LINK_IFELSE at all when LDFLAGS are flags to the LD process.

It is only DED_LD on some platforms (solaris) that use ld as the linker right now.

I don't think doing this should break anything, but it is hard to know for sure.