Test framework documentation should document every single optional argument

[Voileexperiments]

It wasn't until I looked at cw-2.js again that there's actually an option optional argument after msg in the first place, and even with that I have to look all over the code to slightly figure out what it does: it's completely undocumented. (Or the asyncTimeout argument in describe/it, that's also completely undocumented). Similarly, allow_raise is undocumented for Python, and SQL's run_sql has tons of important and useful optional arguments.

The documentation should include every single one of these optional arguments, otherwise it's severely limiting the actual power of the test suite.

┆Issue is synchronized with this Clickup by Unito

[kazk]

For cw-2.js, I left some of those undocumented because it's unreliable (and/or very limited) and didn't want to be used. I'm going to work on cw-2.js soon and undocumented features will change or removed. I'll try my best to keep them mostly compatible.

codewars-runner-cli was not documented well. I'm working on fixing that, but I need to finish higher priority tasks first. Most of the undocumented features at the moment should be considered unreliable.