feat: have `forge verify-contract` take standard JSON input

[CodeSandwich]

Component

Forge

Describe the feature you would like

Verification of contracts after some time passes is tricky because the metadata content changes with Foundry updates (e.g. #8611, but I also noticed it myself). This seems to be a difficult problem to solve globally, so it's better to work it around by keep the standard JSON input generated during the contract deployment. Such JSON can be reliably submitted later, probably using different Foundry version, different tooling and a new scanner. Unfortunately forge verify-contract doesn't accept standard JSON input, it always wants to compile the current sources using its latest logic. This forces the user to use the scanners' web APIs, which accept the JSONs, but are clunky and slow. Using foundry's CLI would be so much move convenient.

Additional context

No response

[tushar994]

I would like to take a look at this, should I?