I can validate a scenario definition file using the CLI

[deepbrook]

Analysis

Current State

When writing a scenario defninition file, it only raises issues with its syntax during scenario execution.

Problem

Executing a scenario completely requires a keystore file, password, data path, as well as funds.
While this is possible to have, it's also a pain in the ass to pass to the CLI. Additionally, the only other tool at hand is an online yaml validator, which requires the user to copy/paste the scenario definition into an online tool. This, however, does not check for valid input types (str, bool, lists, dicts), but much rather only checks that a yaml parser can read it.

Solution

Supply a new CLI command, scenario_player lint <scenario-file>, which lints the scenario definition file against a yaml schema, in addition to checking for mutually exclusive options, and validity of tasks.

---