🐡 Inflate `__cxa_throw/rethrow` unwind instructions

[kammce]

We currently unwind manually by looking at the disassembly and unwinding manually in the code. If the code changes, this would break the manual unwinding. We can save on cycles by searching for and caching the location of the __cxa_throw and __cxa_rethrow table entries on system boot up. That way the system can benefit from faster unwinding throughout the duration of the application. On ARM Cortex M, this would cost 8 bytes total for the two pointers.

[kammce]

Maybe this has been failing because I never used the __wrap___cxa_throw and instead used the original unwrapped name 🤔

[kammce]

Actually a better option would be to search and cache the unwind instructions for both throw and rethrow, that way we can just directly unwind them against the snapshot of the CPU. No need to go through all of the fuss of evaluating the entry and converting it into an ordered list of unwind instructions.