Inline resetTimer for all platforms

- for arm generic timer platforms, we remove resetTimer ->
resetGenericTimer indirection and simply include generic_timer.h
- this reduces boiler plate for platforms that share timer drivers, as
they simply include the one header
- there is far more timer code in the RT kernel, which motivates this
change

Move arm generic timer to own header

Only platforms that use it should include the code

Combine common arm generic timer code

Previously both aarch32 and aarch64 duplicated common
generic timer code. Unify them in include/arch/arm/machine/timer.h

arm/imx7: add/correct dev mem/int; generic timer

Add more device memory regions and interrupts.
Merged Anna's generic timer impl.

Fix arm builds broken in 44ed6adb6

SELFOUR-607: inline remaining irq path functions

SELFOUR-519: remove map_kernel_devices duplication

* move devices to static array in hardware.h
* use one higher level function to map them in.

SELFOUR-519: remove more duplication in hardware.c

* move p_reg functions up a level
* move p_reg definitions to hardware.h

Refactor duplicated code in hardware.h

One copy to rule them all.

Trivial: move printfs in handleReservedIRQ up.

This wraps the printfs in CONFIG_IRQ_REPORTING
and reduces redundancy.

SELFOUR-402: remove isReservedIRQ

While provided by each hardware platform this function is never called.

SELFOUR-446 Benchmark: Track syscall feature

Benchmark feature that currently:
- Keeps track of system calls info
- Start time
- Duration
- Capability type
- Invocation tag
- Log the number of invocations of each system call*
- Log the number of invocations for each capability type per syscall.
- Has 3 new syscalls (dump, reset, get size).
- This new feature uses the existing log buffer (which is 1MiB for x86
and ARM). Since the number of syscall invocations is not
deterministic, the logged number of invocations is limited by the size
of the buffer. I suggested to enable the users to pass their own
user-level buffer, to enable more flexibility, later.
- ENABLE_BENCHMARKS is now a parent config option of trace points and
system call track features, they can't be used at the same time.

Further separate 'release' and 'verification' builds

Originally building the kernel was largely considered to be done in
one of two ways
1. Release build with no assertions, no debug symbols and no printing.
This was generally considered to be a 'verified' build
2. Debug build with assertions, debug symbols and printing

Since then various options were added, such as the 'code injection'
option, which we wanted on builds that did not have assertions or
other options that affected performance. As such it did not depend
upon a debug build and had large warning signs saying that enabling
this in a release build would not give you a verified or trusted
kernel.

Most recently the ability to print from the kernel in release mode
was added. For the same reason that tying the ability to print with
the performance reduction of various debugging was not always desireable.

This change attempts to unify the current state and have a single top
level option to enable a 'verification friendly' build. All other
options (assertions, printing, code injection) then depend upon
this configuration not being set.

trivial: make style commit

arm/imx7: add support for iMX7-based Sabre board