Feature/3307/detect-invalid-file-input

[moritz-suckow]

Detect invalid file input

Issue: #3307

Description

This PR adds validation for file input for all parsers, by checking a row of conditions (existence, non-emptiness, ..., for details look at the specification in the issue).

[moritz-suckow]

Regarding the code smell from Sonar: I would ignore it. Moving the return out of a double nested if, is in my opinion, not good for the code's readability.

[moritz-suckow]

Currently this feature is implemented in a way, that invalid resources can only be detected when running a command. That means when using the interactive parser or parser suggestions, the user first answers all questions to configure the parser, the parser/s start/s running and THEN the user gets warned if files/folders do not exist or are invalid.

Is that okay for now or should this PR also implement a warning when configuring?

[phanlezz]

Small thing that should get changed:
Currently there is no error code, if a parser get stopped after configuration, and the "parser suggestions" thinks it executed correctly. -> Still tries to merge in the end
A user could miss the fact that one parser did not execute -> The hole execution should stop

[sonarcloud]

[CodeCharta Analysis] Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

96.4% Coverage
0.0% Duplication

[sonarcloud]

[CodeCharta Visualization] Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[phanlezz]

LGTM

[moritz-suckow]

Maybe after changing the action following invalid input from just printing a message and returning to throwing an exception we should also adapt the tests to check if an exception gets thrown?