feat: allow any config to be defined inline

[DaniPopes]

Allow any configuration value to be defined inline using the same TOML syntax as foundry.toml.

This is achieved by updating Config, Executor etc. fields with the new inline Config value saved in a TestRunnerConfig field for each level of tests:

• MultiContractRunner, global
• ContractRunner, contract-level, applied before running any EVM code
• FunctionRunner (new), function-level, applied before running each test

TestRunnerConfig is inherited from the level before, and updated with inline config whenever it's available.

Not all configs will do something at every level; for example the fork stuff is spawned at contract-level so changing that at function level won't have any effect, but for that there is cheatcodes.

TestOptions's functionality has been moved to FunctionRunner.

Closes #8564.
Closes #6908.
Closes #6228.

[grandizzy]

Awesome stuff! gave #6228 (comment) a try with inline paris and shanghai and works great. I think this PR should close #6228 too per #6228 (comment) (1st and 3rd bullets are covered in this PR, the 2nd bullet / automatic detection is tracked in #6440)

should we clean up tests a little bit too (like merging testdata/paris in testdata/default and removing the TEST_DATA_PARIS / paris ForgeTestProfile profile and using inline config for specifying the evm version), or better to keep separate profiles? (I can follow up in a PR after we merge this one)

[grandizzy]

lgtm!

[mattsse]

hell yeah

[smartcontracts]

@DaniPopes should this PR make it possible to set optimizer_runs for a specific contract? I tried /// forge-config: default.optimizer_runs = 5000 without any effect

[grandizzy]

@smartcontracts you may want to check compiler profiles and compiler restrictions added in #8668