lobsterparser: fix incorrect warning logic

[ondracka]

Just something I messed up in the last patch, the parsed results were OK, just a warning was printed when it shouldn't be so add also few simple tests to catch this in future.

[ondracka]

CC @ladinesa

[ondracka]

I think this might have been forgotten... its really trivial.

[ladinesa]

Sorry I missed this, can you please send me the test files?

[ondracka]

It is reproducible with the checked in test cases I even included some pytest testing.

[ondracka]

Hm, actually I see this was fixed by you in unrelated commit 069f068 already.
So unless you want to commit the tests that a correct amount of warning is emitted, this can be dropped completely

[ladinesa]

Hm, actually I see this was fixed by you in unrelated commit 069f068 already. So unless you want to commit the tests that a correct amount of warning is emitted, this can be dropped completely

I will keep this open and work on it when I get back.