feat: make deployment order optional

[0xPhaze]

For improved user experience, we could simply deploy contracts in an arbitrary (alphabetical) order. I think in most cases it might not matter what the order is. This should be an optional feature.

error Failed to initialize the test chain
‣ you must specify a contract deployment order within your project configuration

[anishnaik]

So deploymentOrder unfortunately cannot be optional. It is equivalent to --target in echidna. You have to tell medusa what to actually fuzz test. This is a mistake we made when naming the configuration options in medusa. Think of deploymentOrder as a list of targets. While Echidna allows you to fuzz only 1 target at a time, medusa allows you to target more than one. At the end of the day you only want to deploy things to the blockchain that you actually want to fuzz test. Alphabetically deploying everything would not tell you what to actually fuzz test at the end of the day.

This is in contrast to the compilation target. This, unfortunately, in medusa is called --target src/Counter.sol whereas in echidna it would be echidna src/Counter.sol.

We have a PR that will change the config options as follows:

• deploymentOrder -> targetContracts
• target -> compilationTarget

Lmk if you have any further questions, otherwise will close this issue.

[0xPhaze]

Ah I see, that makes sense. Closing then.