Add support for config file and refactor run config parsing

[BowTiedRadone]

This PR:

• decouples run configuration parsing from main to keep the entry point clean
• adds a --config flag for file-based configuration
• adds support for pre-specifying custom accounts (allowing mainnet addresses to be used without providing their private keys by leveraging simnet remote data) using the config file

Fixes #183.

[moodmosaic]

Very nice refactoring 👍 A few comments below (and inline):

---

I think, a user typing:

rv ./project counter test --config=rv.config.json --seed=999

would have no indication that --seed=999 was discarded. Perhaps worth considering emitting a warning via the radio when both sources are present?

---

I also think that a typo like { "sedd": 42 } would be silently accepted as an empty config(?) If that's the case, consider warning on unrecognized keys.

[moodmosaic]

If a user passes --seed=abc, parseInt("abc", 10) produces NaN, which will silently propagate into fast-check as the seed. The config-file path validates this properly ("seed" must be an integer), so there's an asymmetry.

[BowTiedRadone]

122f9be

[moodmosaic]

This now excluded faucet, right? If this is intentional, a comment would help(?)

[BowTiedRadone]

8f74d90

[moodmosaic]

The catch branch always calls process.exit(1) (which returns never). An explicit annotation would make the contract clearer for readers

Suggested change

	const parseCliOrExit = (argv: string[], radio: EventEmitter) => {
	const parseCliOrExit = (argv: string[], radio: EventEmitter): RunConfig | undefined => {

(Might have to be formatted to fit the 79-char width.)

[BowTiedRadone]

5905ad8

[BowTiedRadone]

@moodmosaic Thanks for the review. All should be addressed now