Providers depending on fog-core need to be *all* bumped to v2+

[gildub]

For the providers having a dependency on fog-core, being able to bump fog-core version to 2+ require to do all of them in an atomic way (everything or nothing).

Fog-core 2+ main impact is around namespace: Fog::<Service Name>::OpenStack for instance becomes Fog::OpenStack::<Service Name>. This is not mandatory but will generate deprecation messages. Therefore this can be done in 2 steps, bump fog-core and then later on realign namespace.

The current providers using fog-* projects are:

• manageiq-providers-openstack
  • fog-openstack:
    • 1.0.0 is fog-core '~> 2.1' with updated namespace
    • 0.3.0 is fog-core '<= 2.1.0' and no namespace update
• manageiq-providers-google
  • fog-google:
    • 1.5.0 uses fog-core '>= 2.0', '<= 2.1.0'
    • 2.0 will have updated namespace and fog-core '~> 2.1' => Bump fog-core version to ~> 2.1 fog/fog-google#422
• manageiq-providers-kubevirt
  • fog-kubevirt
    • 0.1.6 requires fog-core '1.45'
    • Next release will be fog-core '2.1.2' (with namespace change)
• manageiq-providers-vmware
  • fog-vcloud-director current '0.3.0' supports up to fog-core '2.1.0', has its namespace updated
  • fog-core direct dependency has been removed
• manageiq-gems-pending
  • fog-openstack dependency needs to move to v0.3 => bump fog-openstack to v0.3 manageiq-gems-pending#386

[aufi]

👍

[gildub]

All projects are now supporting fog-core to version at least up to 2.1.0.