🐛 Fix potential crash encrypting with Modcrypt, invalid header hash generation and corruption of Modcrypt after arm9 changes

[pleonex]

Fix several bugs related to Modcrypt (d)encryption and ROM header hash generation, especially after changes on the arm9 and/or its code parameters (such as compression length):

• Potential unhandled exception, calculating the key for Modcrypt (d)encryption for retail software. This may happen during ROM reading or writing.
  • The reason is that by default BigInteger are signed values and after the bitwise OR operation, the sign may be affected changing a 22-bytes length number to a 6-bytes length number.
• Fix generation of arm9 secure area when its code parameters changes. The hash was calculated with arm9 content before patching the code parameter values such as file compressed length.
• Fix program HMAC generation: it was calculated with an old value of arm9 secure are hash
• Fix corruption of modcrypt content: the content was encrypted with an old arm9 secure hash which is part of the key.

Also fix the build by installing .NET 6 SDK and bumping .NET 8 SDK.

Quality check list

• Related code has been tested automatically or manually: tested with the problematic software and updated tests
• Related documentation is updated
• I acknowledge I have read and filled this checklist and accept the
  developer certificate of origin

Acceptance criteria

The Modcrypt key generation does not fail.
Every hash of the encrypted content is valid after changing the arm9 content.

Follow-up work

None

Example

N/A