Separate out keystone registration calls from other recipes

This will allow us to be more efficient with our chef-client stuff, and only execute the keystone registration calls on a single host instead of every controller node that has glance::api or glance::registry recipes in their run list.

Verified in DAL2.