Workaround for a GCC bug (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58930)
Triggered with the bebop toolchain.

This has changed as we changed to TCP with the lockstep implementation.

 * The build is built with SPI4. At run time the signal GPIO_8266_GPIO2 it tested. If it is low the SPI4 is configured. If it is high SPI4 is not configured.
 * board_common: Add Notion of Board has bus manifest

As reported by @LeoMustafaNXP in https://github.com/PX4/Firmware/issues/11296

* Jenkins: no SITL entrypoint for now
* Jenkins: complile - no snapdragon eagle entrypoint for now

ToneAlarm class refactoring to implement an interface for hardware specific methods and a single ToneAlarm class.

 - Jenkins compile drop arch until container is updated and maintained
 - clang-tidy disable for now, the new version isn't respecting the existing configuration

uorb_to_ros_msgs: delete all messages on the out dir first, so it can also consider message deletions on the input dir

Some threads do not exit and are still running when
trying to exit SITL running under Windows in Cygwin.

This problem was introduced with:
- posix shell #10173 because of strating a child process
for the startup script and mixing up the signal handling
(only Ctrl+C broken)
- lockstep #10648 because of simulator threads not
stopping gracefully anymore with timing race conditions
(no graceful exit possible anymore)

I leave the SIGINT handler on its default implementation for
Cygwin which kills the process and all its threads when pressing
Ctrl+C.

This hotfix at least allows the usage of Ctrl+C again instead
of forcing the user to use the task manager to shut down
px4.exe going crazy on CPU load instead of exiting
everytime.