Send User object to new employee page

When "Submit" is clicked after signing up, it redirects to an
employees/new/:id page. The :id that is sent corresponds to the new
User's id, which the employee controller looks up.

TODO: Autofill name and email field with user info and disable it
Commit all before CRUD user

I don't know if this commit is working, but this is the commit before I
start modifying files in accordance with the CRUD user files
CRUD Users and Registerable

The program can now create new Users two different ways:

1. If there is no one signed in, and the "sign up" button is clicked, a
new user is "registered" and automatically signed in

2. If a signed in user clicks "new user", then a new user is created
without signing the first one out

TODO:
1. Change employee to profile
2. Pair each user with a profile
3. Only allow admins+ to access the users pages
Registration routing (final CRUD)

Users can sign up
- Redirects to new employee page
Signed in users can make new employees
- redirects to new user, which redirects to new employee page
Add Profile to Model

Added Profiles and logically included them in the same places where
Employees are. I tried to limit the amount that "employees" were
completely taken out. I also expanded some Profile functionality,
especially in regards to its relation with User. Specifically, I set the
model up so that Profiles and Users are one-to-one, bi-directional, and
dependent. Also, a User object that is retrieved from a Profile object
is read-only, for security. I also added some helper functions in
Profile that take advantage of the information already housed in User
(such as name, email, and permission level)
Updated readme

Added StaffInSight logo
Employee functionality removed

While employees are still in the schema, all their functionality and
naming have been removed from the logic
Employee Deprecated

Everything having to do to "employees" has been removed from the system.
This includes both logical and cosmetic changes. The application has
been thoroughly tested to ensure no conflicts arose, and everything
works. The new term for Employee is Profile, and sometimes cosmetically
Profiles are called Staff (for logical clarity)
Started CanCan Authorization
CanCan for Profiles

Authorization has been implemented for everything having to do with
Profiles
CanCan for various; incomplete

Implemented some more CanCan authorization, but waiting on a more
detailed requirements list from Jake
Remove employee migrations
Added a single "up" migration

This migration will build the correct schema from scratch
Merge remote-tracking branch 'heroku/master' into clean-migrations

Conflicts:
	README.md
Cleaned out migrations
Deleted other migrations
Merge branch 'master' of heroku.com:staffinsight into clean-migrations
Removed the schema file
Fixed typo in migration
Changed after_sign_up_for to resource.id