Replace KGOs in CI script?

[dustinswales]

Problem: Having to update the KGOs is somewhat of a bottleneck in the code review process, as it cannot be done by all COSP code managers. Also, it requires us to maintain versioning within the codebase.

Potential Solution? Within the CI scripts, run the offline COSP tests twice. Once with master (i.e. latest KGO) and once with feature (i.e. new KGO), then compare.

@alejandrobodas This would be straightforward to implement in the CI scripts. Thoughts?

This would supersede #50

[alejandrobodas]

@dustinswales I like the idea, but I see one potential issue. We'll be unaware of changes in the KGOs that are caused by external dependencies, e.g. changes in the ifort compiler. This has happened several times in the past.