Wallet deploy and test

[dmtrskv]

Generating and deploying new wallet if one does not exist. First of all, required for tests (we have no other reasonable way to create a wallet in hardhat tests actually, because we must inject it into the handler context). But also can be useful for cli use, so that a user won't have to use nil_cli.

The private key is required by hardhat, so we shouldn't generate it.

Here I generate the wallet address if it is not provided.
If the wallet is not deployed to the address (either provided or generated), then it is deployed.

For this I fixed extendEnvironment which actually contained a race between the test and the setup (due to async func being called before setting up send and request functions; we should wait inside them on the promise).

The second commit introduces incrementer ignition module from example and a script running it. I think we'll need a trivial test of the hardhat cli of such kind.

[dmtrskv]

I do not get why build on 22 fails.

[0xAleksaOpacic]

I do not get why build on 22 fails.

@dmtrskv Hey, just check the issue and it is related to node version.

To be more specific our GH action is using v22.5.0. And in the GH action you can see that installation failed:
https://github.com/NilFoundation/nil-hardhat-plugin/actions/runs/10009987332/job/27675560764?pr=19#step:3:50

I tried locally to use this version and have the same issue. I checked the latest release and found these is a patch fix v22.5.1. Tried locally using this version and no issues.

If you checkout this release you can see that it fixes the error we have: Exit handler never called! (https://nodejs.org/en/blog/release/v22.5.1)

This fix was release 3h ago, so i assume it will just take some time to propage version, @ukorvl an i right?

[dmtrskv]

Merged the commits and moved tests to the tests directory, so that they don't spam plugin structure with contracts and other hardhat dirs.

[0xAleksaOpacic]

Than you for opening PR and adding this!