Add modm_abort() as a non-recoverable modm_assert()

[salkinium]

Assertions were intended as a low-cost alternative to C++ exceptions, see https://blog.salkinium.com/xpccs-error-model/.

However, there are three issues:

• modm_assert_debug() resolves into a no-op for release mode, which isn't useful.
• modm_assert() is recoverable by the user by returing Ignore from the assertion handler.
• modm_abort() or similar should be added that ignores the assertion handlers and always abandons. Or should there be a way to call modm_abandon() directly?
• the failure string is too costly and too restrictive:
  • there isn't always a clear module, location and failure, leading to duplicated module and location strings.
  • there should only be one string passed as the reason, and the library developer is responsible for creating namespaced, unique failure strings. A naming convention inspired by reverse-domain notation (ie. separation by . dots) could be encouraged.
  • strings should optionally be placed into a GNU comment section and only their index is passed to the assertion handlers (there needs to be a way to reverse lookup this).

[salkinium]

There should be a short error location string given, and also a full text reason that is placed only in the ELF file. In addition the call location (PC?) should be recorded, with an optional stack backtrace printer for the abandon handler.

[salkinium]

Another thing is to replace modm::ErrorReport with assertion or similiar.