Use stricter flags for native toolchain

[celskeggs]

F´ Version	v3.5.1
Affected Component	build system

---

Feature Description

The native toolchain uses lax compiler options defaults. I suggest defaulting to the following options:

    -std=c++14
    -pedantic
    -Wextra
    -Werror
    -Wold-style-cast
    -ggdb3

Rationale

The JPL Institutional C++ Coding Standard mandates the use of C++ 14 with "all compiler warnings enabled at the highest warning level available, with no errors or warnings resulting." The native toolchain currently defaults to -std=c++11 without -Werror, which means that flight projects need to provide their own UT toolchain configuration in order to comply with the standard. It would be sensible for F Prime to provide a default toolchain configuration that is already compliant with institutional standards to make things easier for flight projects, especially since it results in higher-quality code.

I also recommend the use of -ggdb3 to provide higher-quality debugging information than the current -g.

[astroesteban]

To add to this great suggestion, the Open-Source Security Foundation (OpenSSF) has a compiler options hardening guide that would be useful to reference for core product security as well:
https://best.openssf.org/Compiler-Hardening-Guides/Compiler-Options-Hardening-Guide-for-C-and-C++.html

There is also a CMake example someone put together:
https://www.stevenengelhardt.com/2024/11/12/cmake-implementation-of-openssf-compiler-hardening-options/

[LeStarch]

We need to do the following:

1. Add in default set of flags that F´ supplies
2. Reporting for which flags are used.

[LeStarch]

See #3924