Task module response prototype

Setup table structure and restructured some task modules/forms to store student responses in a table consistently. This also allows the task content to be dynamically displayed and maintained more consistently, while allowing the creation and reuse of modules.
> The module is generic and can be reused, so we wouldn't want the configuration there. However, in thinking about this, a cleaner way to do this would be to create an accessor method on the task_section model that automatically parses and returns the JSON. Before we go that route though, I think it would be good to have a conversation as to whether or not it makes sense to keep storing it as JSON, or attempt to move it to database fields (which would make the JSON irrelevant).

My thought is that we keep JSON for now for speed of implementation purposes.  I think moving to name/value pairs or some other way to store it more structured in the database is going to be harder to move quickly in making changes.