Refactor pragma usage in C/C++ code by using dedicated include files

[jimklimov]

PR #3590 has demonstrated the possibility of using headers to offload repetitive code like pragma start/end incantations we use to quiesce certain warnings (like when compilers both require all pre-known switch/case possibilities to be covered including a default, and that it would never be visited for an enum with all values listed explicitly).

This issue is a relatively low-hanging fruit about identifying pragma combos that are frequently used, and replacing such instances with header files to begin and end a block by a couple of dedicated include files per combo (not sure "header files" would be the right term if we #include them many times in the middle of C source code). This would significantly shorten actual codebase in some files and make it more readable and maintainable.

Kudos to @user01010111 for being the first to try this idea in practice!

[biergaizi]

Strongly approve this PR.

These pragmas were added during a project refactor campaign called "fightwarn" with the goal of suppressing all compiler warnings. Unfortunately, because it was rushed, the fixes themselves are often "brute-force" in nature. If the compiler says there's an integer overflow, the fix was to cast all possible integer values instead of fix the location of the overflow. If the compiler says there's a buffer overflow, the fix (even to a compiler false-positive) was to add range-checked in all locations where the value is used, rather than fixing the logic.

For example, one commit was introduced to the driver I maintain to suppress an integer overflow warning:

crc16_recv = (uint16_t)((uint16_t)(ident_response_end[0]) << 8) | (uint16_t)(ident_response_end[1]);

I later reverted this change because it was clearly an overfix.

These GCC pragmas are my most disliked commits during the fix. If these changes were subject to review of the maintainer of the respective drivers, I would have rejected them in my driver immediately. Sharing them into a standard header is a choice that I would make from the beginning, if the I don't understand why the copy-and-paste approach was used in the first place.