Add verification helper tool

Add some logic to assist in mod verification (https://github.com/R2Northstar/VerifiedMods/)

In particular

• easily create diff to last verification if it exists (to allow for fast re-verification especially when there's only small changes)
• flag "dangerous" calls to native (in particular Safe I/O and SquirrelHTTP, while on it's own not dangerous at all, they can be used to add additional logic that is impossible to verify using solely automated static analysis and require the knowledge of a human reviewer to ensure safety)

Features

downloader

download version requested for verification

diff creation

1. download last verified version
2. extract
3. git init
4. git commit with some dummy user
5. delete all files except .git folder
6. download version requested for verification
7. extract into same folder
8. stage files without committing
9. launch vscode to then easily see diff

"dangerous" keyword finder

simply do string search over the code and flag for certain keywords that would require additional scrutiny (SquirrelHTTP, SafeI/O, ...) or should be ban the mod entirely from verification (compilestring).

No files or tests are named. Start by locating FlightCore's Rust/Tauri entry points and reviewing how a verification helper could handle downloading and extracting versions, creating the requested Git diff, and scanning code for flagged keywords. Done means the requested version can be compared with the last verified version and dangerous or banned calls are clearly reported for review.