Add jar argument to spark_rapids CLI

[amahussein]

Signed-off-by: Ahmed Hussein (amahussein) a@ahussein.me

Fixes #901

[nartal1]

Thanks @amahussein ! LGTM.
Have a question:
What should be the behavior if the tools_jar version doesn't match with user-tools. i.e if the user accidently provides the old tools_jar version path, should we throw an error OR let it go through using the old jar itself? Or do we already have a check in place for this.

[amahussein]

Thanks @amahussein ! LGTM. Have a question: What should be the behavior if the tools_jar version doesn't match with user-tools. i.e if the user accidently provides the old tools_jar version path, should we throw an error OR let it go through using the old jar itself? Or do we already have a check in place for this.

Since, we cannot verify the version from the file's name, the way to do it is to process the POM file inside the jar to check the version. This implies that users with custom builds/versioning won't be able to use their jars against the CLI. Rendering the feature to be useless.

So, I would say that it is user's responsibility. Even if we process the pom to display a warning without completely bailing out, the benefit is not worth the effort IMHO.

[cindyyuanjiang]

LGTM, thanks @amahussein!

[parthosa]

Thanks @amahussein.