feat(cheatcodes): forge execution context check

[grandizzy]

Motivation

Closes #2900

Solution

Add a global /execution context based on forge subcommand used - can be set only once per program, and it can be checked by using isContext(ForgeContext context) env cheatcode.
ForgeContext have following options:

• TestGroup: Test group execution context (test, coverage or snapshot).
• Test
• Coverage
• Snapshot
• ScriptGroup: Script group execution context (dry run, broadcast or resume)
• ScriptDryRun
• ScriptBroadcast
• ScriptResume
• Unknown

[DaniPopes]

lgtm, pending another review. CC @mds1 @mattsse @klkvr

[Evalir]

lgtm! test failures seem spurious, so waiting on another review

[grandizzy]

lgtm! test failures seem spurious, so waiting on another review

yeah, according to https://github.com/foundry-rs/foundry/blob/master/docs/dev/cheatcodes.md

The initial execution of this command, following the addition of a new cheat code, will result in an
update to the JSON files, which is expected to fail. This failure is necessary for the CI system to
detect that changes have occurred. Subsequent executions should pass, confirming the successful
update of the files.```

[DaniPopes]

It's not spurious, you have to run the command locally as the output and doc suggest

[mattsse]

lgtm

[mattsse]

@grandizzy I ran cargo cheats, which perhaps broke a few things in sol files

[grandizzy]

@grandizzy I ran cargo cheats, which perhaps broke a few things in sol files

@mattsse yeah, sorry, my bad, was something I missed for adding the new enum, should be fixed now (forced pushed your commit). @Evalir 's comment re CI failing was a legit concern 🤦‍♂️

[Evalir]

yep @grandizzy sorry for the confusion here—first CI failure comment seemed spurious but below there was the cargo cheats message