chore: add contribution guide and document scripts/vm.py

[zerosnacks]

Copied from https://github.com/foundry-rs/foundry/blob/master/CONTRIBUTING.md with some minor modifications to make it specific to forge-std

Documents running vm.py to update src/Vm.sol in more detail, related: #615 (comment) as well as the new --from flag

[Tudmotu]

To generate the changes from my PR on Foundry repo I had to manually modify vm.py to fetch the json from my repo+branch.

It would be nice to be able to pass that information to vm.py, something like:

$ ./scripts/vm.py tudmotu vm.mockCalls

And it would fetch the json file from https://raw.githubusercontent.com/{username}/foundry/{branch}/crates/cheatcodes/assets/cheatcodes.json

These params could be optional and default to "foundry-rs" and "master" respectively, to keep backwards-compatibility.

WDYT?

[zerosnacks]

To generate the changes from my PR on Foundry repo I had to manually modify vm.py to fetch the json from my repo+branch.

It would be nice to be able to pass that information to vm.py, something like:

$ ./scripts/vm.py tudmotu vm.mockCalls

And it would fetch the json file from https://raw.githubusercontent.com/{username}/foundry/{branch}/crates/cheatcodes/assets/cheatcodes.json

These params could be optional and default to "foundry-rs" and "master" respectively, to keep backwards-compatibility.

WDYT?

Ah I see, I generally wouldn't be against making this addition

In terms of process it is usually the case that cheatcodes are first merged and then a follow-up PR in forge-std is to be drafted rather than concurrently. Defaulting to the existing case is a good middle ground I feel.

Would you like to contribute this change?

[Tudmotu]

Sure, will open a small PR using argparse and you can decide if you want to include it.

Edit: #619

[DaniPopes]

we probably should remove this

[zerosnacks]

I think this could still be useful as users generally don't know the distinction between Foundry / forge-std

Or are you in favor of deprecating either / any support portals? We haven't seen a lot of use of the Github discussions but it is a good place to find answers if we clean it up a bit

[zerosnacks]

Can be handled in a follow-up if desired cc @mds1

[DaniPopes]

Sorry I mean the discussions.

[zerosnacks]

Going to merge as it is relatively non-controversial and should help external contributors to run / update

Happy to handle any follow-ups / modifications