DigitalOcean will change their floating IP API on the 26th of april

[vdloo]

We just got an email from DigitalOcean stating that they will change their Floating IP API endpoint starting the 26th. Functionally this shouldn't break in libcloud but the fixtures for the tests that are used will be a bit outdated (https://github.com/apache/libcloud/blob/trunk/libcloud/test/compute/fixtures/digitalocean_v2/list_floating_ips.json)

Changes announced by DigitalOcean:

The `private_networking` feature will now be listed under droplet.features instead of region.features
vpc_uuid was not being populated and will have the correct values now
The droplet.type will be "base" when the droplet is a base image (i.e. Ubuntu, CentOS).
The current value is "snapshot"
The Droplet's networking field will include any private IPs and any floating IPs which are missing from the response today

Test fixtures that would become 'inaccurate': https://github.com/apache/libcloud/blob/trunk/libcloud/test/compute/fixtures/digitalocean_v2/list_floating_ips.json https://github.com/apache/libcloud/blob/trunk/libcloud/test/compute/fixtures/digitalocean_v2/create_floating_ip.json

[stale[bot]]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.