Tasks Backend

I think I am done. Finished tasks_controller methods, model validations/methods, basic unit testing for tasks and mailer configurations and views (fixes #106 )

Currently, all task tests are failing, with the error `NoMethodError: undefined method `name' for :task:Symbol`.

I think the problem is related to name field of admin. That made me realize several things:
1. We didn't do the separation of `first_name`, `middle_name`, `last_name` for the `Admin` class. We probably should do that.
2. Also, I didn't see any validations for the presence of name-related fields in both `Patient` and `Admin` models. Shouldn't we have them?
3. When you are reviewing, please put more attention to tasks_controller.rb and task.rb. I wasn't really sure about how I should formulate the kinda circular relationship of assigner and assignee through the `Admin` class. 
In that given case, Nancy would be the assigner, but I agree with its uselessness.. I somehow thought it might be useful. Also, in its current form, the tasks are not automatically created. At its current format, I am imagining there will be some sort of a form that an admin would fill and assign an task to another admin.

I was planning on automatic task generation for a v2 for the Tasks feature, to speed things up. But I will see what I can finish by tomorrow.