Fix: ensure new fog works with ec2

One fix involves how security groups were being cached in ironfan
with a prepended 'vpc-deadbeef:' but lookups are later performed
without the prefix.  The fix is to cache the security group with
both prefixed and non-prefixed keys, to guarantee non-breakage in
other cases.

The second fix is to text matched in an error message about duplicate
security groups that we were matching/ignoring.  The error text
changed somewhere upstream, so we widened the net on how the text
is matched.

Change-Id: Ie98d558fd95e1e54fe67592e10dc61ce8aac53a2
fix: non-vpc security groups no longer use -1 ip_protocol

Change-Id: I2735222e6a93f59c4cfe87f7984cff9567de3d14
version bump to 6.0.5

Change-Id: I4aa6825f0f587328b7f67adc04717de5dada1771
Fix: cloud-init in openstack uses top-level userdata

Change-Id: I79821b729326999c728e0803536d18c0738c35d6
Merge "Fix: cloud-init in openstack uses top-level userdata"
Merge "version bump to 6.0.5"
fix: string cluster names

Previously, string cluster names in realms did not work.

Change-Id: I1368ad13719f2222afcc8f71d9d26a4ef6bd1d65
version bump to 6.0.5

Change-Id: I145892d8534da23067510259f973afc75649595e
fix: add unf as a gemspec dependency

Change-Id: I978ce0c23ff1d7568c29d3270db78f0c46d3eac1
Merge "fix: string cluster names"
Merge "version bump to 6.0.5"