BitBox02 firmware

This commit adds a new simulator/testing feature that pretends the device is a 'Nova' model. It only touches test and simulator code, not the real firmware that runs on customer hardware. There is no indication of a security bug or fix.

This is a routine dependency cleanup in the BitBox02 hardware wallet firmware. The developers removed a direct dependency on a small library called 'bech32' and instead started using the version that is already included through the larger 'bitcoin' library. The actual code behavior is unchanged; this is purely about simplifying package management and avoiding version mismatches.

This commit only reorders #include lines in a test helper file to match the project's code formatting rules. It makes no functional change and has no security relevance.

This commit is a routine internal cleanup: it changes a cryptographic signing helper so that callers pass in the secp256k1 library context explicitly, instead of the function fetching that context itself from an internal helper. There is no direct security fix here and no evidence of an exploitable bug being patched. It is a step toward removing a dependency on an old wrapper function (`wally_get_secp_context()`).

This commit is a small internal cleanup: it changes a Bitcoin signing function so that the caller provides the cryptographic context, instead of the function fetching its own. There is no visible bug fix or security patch in the diff itself, and no security relevance is stated by the vendor.

This commit is a routine internal cleanup: it changes a cryptographic helper function so that callers pass in the secp256k1 context explicitly, instead of the function fetching a global context internally. There is no direct security vulnerability visible in the diff. It is part of a gradual migration away from an old context accessor (`wally_get_secp_context()`).

This commit is a small internal cleanup in the BitBox02 firmware's silent-payment code. It replaces a locally-created secp256k1 cryptographic context with a shared global one. There is no direct evidence in the commit that this fixes an exploitable security bug; it appears to be a code-quality and consistency change.

This commit removes an unused CMake variable and the code that built it. It is a routine cleanup with no apparent security relevance.

This commit adjusts build conditions so that a low-level hardware reset routine for the Bluetooth chip is skipped during automated unit-test builds. It is a build/test hygiene change rather than a fix for an exploitable security flaw in production firmware. There is no direct evidence that this change was made in response to a security incident or vulnerability report.

This commit only fixes garbled comments in the source code. The actual code logic—mapping Latin-1 byte values to other byte values for display—remains completely unchanged. It is a cosmetic/documentation cleanup with no security relevance.

This commit changes a build-time helper tool so that, instead of crashing with a generic panic when protobuf compilation fails, it prints the actual error message and exits with a clean error code. It is a developer-experience improvement with no runtime security effect on the BitBox02 device firmware.