Bug 1005404 - Add ability to create task within tool

This is my first attempt to implement the features requested by bug 1005404. This includes:
- Changes to the model to support the new metadata for tasks
- A form that an admin can use to create a new task
- A form that an admin can use to edit an existing task
- A listing that an admin can see with all tasks, from whence they can choose one to edit and also can click a button to be taken to the "new task" form

Everything seems to be functional and working, and matches the spec in the bug, including limiting access to admins. The form *does not* look good. It needs css work, and that is far from my forte. I am hoping that someone currently on the project can help with that, or perhaps we can recruit someone to help with it.

As for the django code, I am definitely uncertain about a lot of it, so I am hoping for feedback from @Osmose. As I said, I believe that it all works, but I'm not sure if I did a lot of it correctly, including how I dealt with assets and the .less file.
It doesn't actually need to be kept; the migrations store a frozen ORM, so even if the model is gone the migration can re-create it. This is why the migration says to use `orm.TaskArea` instead of `from oneanddone.tasks.models import TaskArea`. You're using the frozen version instead of the real version. 

If you were using some special feature of the django-mptt model, it'd be a problem, as the frozen ORM doesn't include the custom logic of django-mptt, but since you're only using the `parent` and `name` fields, you should be free to delete this model.