[#1234] Move relevant test cases in ArgsParserTest to RepoSenseTest class

[HCY123902]

Resolves #1234

Commit message:

Move the relevant test cases in ArgsParserTest to RepoSenseTest

The relevance of some test cases currently in ArgsParserTest 
is more on testing the behavior of methods whose main logic stays 
in the RepoSense class, such as the getRepoConfiguration method 
with LocationsCliArguments, rather than testing the behavior of 
ArgsParser.

Moving these test cases to RepoSenseTest will make the test cases
more organized. Additionally, when new methods are added to
the driver RepoSense class, there can be new test cases added.

Let's move the relevant test cases to a new RepoSenseTest class

[gerhean]

LGTM

[dcshzj]

I don't agree that we should move them to a separate class, but I leave it for the seniors to give their inputs.

Also, do assign the tasks to yourselves if you are intending to work on it, or if you have already submitted a PR. This makes the issue tracker easier to navigate.

[0blivious]

Judging by the name and the aspects to be tested, I feel we should still assign them to ArgParser class. @fzdy1914 @Tejas2805

[Tejas2805]

A majority of the testing involves the ArgsParserClass, therefore don't think this migration is necessary. @fzdy1914 your opinion?

[fzdy1914]

Agree that it is trivial to do so. I would like to better classify it as ArgsParserTest also.