update version requirements after semantic versioning

Change-Id: Iffc017c0e78336aab8757d109a84c4833602a1cb
Using ~> versioning

Since we should be performing semver across our cookbooks, we should
lock to the patch version.  It means "equal to or greater than in the
last digit", so e.g. "~> 2.3" means "equal to 2.3 or greater than 2.3,
but less than 3.0", while "~> 2.3.0" would mean "equal to 2.3.0 or greater
than 2.3.0, but less than 2.4.0".
  http://stackoverflow.com/questions/5170547/what-does-tilde-greater-than-mean-in-ruby-gem-dependencies

Change-Id: Ia728af82aab928c42bdf3f3d6b24c2f1b79ae3f7
Added image registration tests

Added registration tests to simply test the args being passed
to the `openstack_identity_register` LWRP.  The identity LWRP
should be tested at a deeper level than the consumers.

Testing args passed to a DSL (&block) is a bit tricky.  The tests
are not ideal, but give us the necessary coverage to catch common
errors.

Change-Id: I41c5f609582f8ceb46ea73788a0a37d557532444
Merge "Added image registration tests"
Proper creation of policy.json

The template definition had an unnecessary not_if
which would never allow for the template to get created
as policy.json is distributed by the package.
We have a similar policy.json being created in the cinder cookbook

Change-Id: Ic19e53157c70194dd68d68ba448a3403a3b8d1d3