feat: add forge mssv command to assist finding the minimum supported solc version for a project

[mattsse]

Add forge mssv command that takes a project and tries to compile it with various solc versions

Ref https://github.com/foresterre/cargo-msrv

[gakonst]

Motivation is that we detected a misconfigured pragma here and I had to manually bisect to find which is the min version that works.

[grandizzy]

we have now forge compiler resolve which for Uniswap contracts for exmaple would output smth like

Solidity:

0.5.16:
├── src/briefcase/protocols/v2-core/libraries/Math.sol
├── src/briefcase/protocols/v2-core/libraries/SafeMath.sol
└── src/briefcase/protocols/v2-core/libraries/UQ112x112.sol

0.6.6:
├── src/briefcase/protocols/lib-external/solidity-lib/contracts/libraries/Babylonian.sol
├── src/briefcase/protocols/lib-external/solidity-lib/contracts/libraries/FullMath.sol
├── src/briefcase/protocols/v2-core/interfaces/IUniswapV2Factory.sol
...

0.7.6:
├── src/briefcase/protocols/lib-external/base64/base64.sol
├── src/briefcase/protocols/lib-external/oz-v3.4-solc-0.7/contracts/introspection/IERC165.sol
├── src/briefcase/protocols/lib-external/oz-v3.4-solc-0.7/contracts/math/SafeMath.sol
...

0.8.26:
├── lib/forge-std/src/Base.sol
├── lib/forge-std/src/Script.sol

I could be wrong but this should solve the case mentioned in this ticket @mattsse @gakonst wdyt?

[zerosnacks]

I think this proposed command would iteratively compile and find the lowest target whereas the compiler version list only displays the versions used in the project, it doesn't help the user guide in finding to lowest compatibility version.

Given that the Solidity compiler team recommends using recent versions and projects / auditors prefer strict pinning this is largely relevant for library authors who usually explicitly choose their supported version (e.g. ^0.8.4 w/ Solady).

I would be in favor of closing as not planned.