Lay down groundwork for registration service.

Let's discuss registration, round 2.
So we really should treat this as a User resource, instead of a Registration resource.  When we send a POST to /users/ we're implying we're creating a new User which is what the Registration resource is doing.  The other benefit of this being a User resource is that we can then put ALL of the CRUD functions for users under one resource and once URI path.