Switching the dependencies to release versions

This changes the library dependencies to use released versions of the core libraries. They were previously depending on SNAPSHOT versions, which are less stable versions. More importantly, the SNAPSHOT versions are periodically purged from the system to save disk space -- this happened recently. Since these libraries no longer exist on community, building becomes difficult.

This MR moves those dependencies to a release version, which is better going forward and allows FOSSA to do the build and get good dependency information. I assert that there are no substantial changes between the SNAPSHOT version I moved from and the latest release version that I moved to. It's difficult to know which commit the SNAPSHOT dependency linked to, since it moved many times, but here are the differences from the last time the SNAPSHOT dependency was listed and the one commit that has the release version (0.7.0). All of these changes were from me, updating versions and references as part of the release process.

• GCP Differences from v0.6.1-SNAPSHOT to 0.7.0
• IBM Differences from v0.3.8-SNAPSHOT to 0.7.0

For the second IBM change, there were code changes between the latest version of v0.3.6-SNAPSHOT and 0.7.0, but they appear to be additions only. I don't think this will impact compatibility.

• IBM Differences from v0.3.6-SNAPSHOT to 0.7.0

Separately, since I was working with FOSSA, I updated the configuration file and the corresponding NOTICE changes resulting from the new module.

As we agreed on the call yesterday, I'm merging these through without approval now that the pipeline is passing.

mentioned in commit 50fc2a7f

merged

added GC IBM MRDependencies Upgrade labels

changed milestone to %M5 - Release 0.8