HMMER3 search adapter produce incorrect results

I worked on ignored/muted XML tests and found that after HMM3 migration from internal to external tool we have an awful regression that always was in the test but has never been addressed: HMMER search results parser incorrectly parses HMMER output: HMMER uses 1..N notation while our parser reads it as 0..N

As the result all HMMER3 results in UGENE are shifted by 1.