Pin iota-crypto, napi dependencies

[cycraig]

Description of change

Pin the iota-crypto dependency to 0.9.1 to fix compilation errors related to bee-pow 0.2.0.

Unfortunately we'll be stuck on this version for a while, so we may have to deal with not being able to pull in requested features from iota-crypto when they're released, such as the aes-cbc feature.

Also pins napi dependencies to 2.2.0 to fix a TypeScript error in the later 2.3.3 version. Commits the Cargo.lock file for the Stronghold bindings to mitigate problems in the future.

Links to any relevant issues

• See [Bug] bee-pow 0.2.0 compilation fails with iota-crypto 0.9.2 bee#1360 for the bee-pow 0.2.0 error.
• See [Bug] Optional async return types generate invalid TypeScript napi-rs/napi-rs#1154 for the napi error.

Type of change

• Bug fix (a non-breaking change which fixes an issue)
• Enhancement (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Fix

How the change has been tested

All crates compile and pass tests locally, including the Wasm bindings.

Change checklist

• I have followed the contribution guidelines for this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[abdulmth]

Why do we need napi-build and napi-derive-backend?

[cycraig]

To pin them to a compatible version for napi-derive to work. Removing them and running cargo update causes compilation errors.