Add ODC version CLI parameter to allow version pinning

[michalszelagsonos]

This PR adds a new CLI option to allow user to specify the version of the ODC so the version does not move on them unexpectedly. This PR addresses #19 which came about when ODC recently jumped to 9.0 and our scans broke since 9.0 is not backwards compatible with 8.x and there was easy way to prevent the new version from being used.

The change allows for local caching of each version so is user specifies v9.0.2 followed by v9.0.4 and then goes back to v9.0.2, both versions will be retained locally and reused if needed.

[michalszelagsonos]

@centi can you take a look at this?

[michalszelagsonos]

@centi Will you create a new release and make it available as a npm package here?

[centi]

@michalszelagsonos I will. But I want to look at the other reported issues as well.

[michalszelagsonos]

@centi Any updates on an upcoming release? I hate to keep pestering, curious on when we can expect one. Even if it is still few weeks out, it would be very helpful to know so we can plan on our end.

FYI, OCD 9.0.8 recently had a regression which broke the scanner again on our end despite it being just a patch update. This feature would have prevented it. Looking forward to having a more stable environment and be able to control the version updates. I appreciate your time and attention on this, thanks!