Parse definition should be checked

**Describe the bug**
Specifying wrong format for the argument of `CommandParser::parse()` will throw numerous general PHP exceptions.

**To Reproduce**
_command.php_
```php
CommandParser::parse(['arguments' => 'wrong', 'flags' => 'also wrong']);
```
```bash
php command.php
```
**Expected value**
```bash
Uncaught InvalidArgumentException: ...
```

**Actual value**
```bash
PHP Fatal error: Uncaught Khalyomede\Exception\NotEnoughArgumentsException: found 0 arguments, but the command requires 1 arguments in command-parser\src\CommandParser.php:200
Stack trace:
#0 command-parser\example\example-1.php(7): Khalyomede\CommandParser::parse(Array)
#1 {main}
thrown in command-parser\src\CommandParser.php on line 200

Fatal error: Uncaught Khalyomede\Exception\NotEnoughArgumentsException: found 0 arguments, but the command requires 1 arguments in command-parser\src\CommandParser.php:200
Stack trace:
#0 command-parser\example\example-1.php(7): Khalyomede\CommandParser::parse(Array)
#1 {main}
thrown in command-parser\src\CommandParser.php on line 200
```

**Version**
0.2.0

**Suggestions**

Start with CommandParser::parse() in command-parser/src/CommandParser.php, especially the path around line 200, and reproduce the example from command.php with the malformed arguments and flags shown. Trace how the input is validated and compare the resulting exception with the requested InvalidArgumentException. Done means malformed parse definitions produce the expected exception instead of unrelated argument errors.

Written by the indexing model from the issue text.