[CLI][FIX] Fixed a bug where parity of arguments mattered too much

[reza0310]

EDSSHARP was meant to be executed with a compiled version but I found it easier, on Linux, to use dotnet and not compile. As such, the command I used to execute the program (so without any argument) had an even number of arguments which didn't work because this program is meant to be used with an odd number. This behaviour being quite arbitrary, I decided to make it more flexible by enabling the program to search arguments wherever they might be.
For the tests, I tried executing the program with arguments in multiple places and it worked (that's not a lot I know XD).

I have read and agree to the Developer's Certificate of Origin 1.1

[nimrof]

Could you give us a little info about the bug?

[reza0310]

Yes so basically argv was incremented twice each loop (once by the for, once IN the loop) and as such only checked argv[0], argv[2] etc... which works with the compiled version but if the command you use have an odd number of words (e.g. using dotnet for example), it checked in between where the --infile, --outfile and --filetype args where and didn't find them... Incrementing only once by loop (twice only when we find what we are looking for) patches this.

[nimrof]

sorry for late review and thanks for the explaining

Looks good