Check if all hardware interrupts are disabled when entering uVisor boot

- always verify if any of the hardware interrupts are enabled when uvisor is initialised
- on debug build fail with a verbose security message explaining that the port is broken and interrupts need to be initialised using uVisor APIs.
- on release build just die & drop over in an endless loop

Start at the uVisor boot or initialization entry point and inspect how hardware interrupt state and debug versus release builds are handled. Verify the behavior for enabled interrupts: debug builds should provide the specified verbose security failure, while release builds should enter the requested endless loop. No test file or entry-point path is named, so identifying the relevant initialization code and test approach is part of the work.

Written by the indexing model from the issue text.