Improve Project table model to avoid db failure

[willemarcel]

Some fields on the projects table are the consolidation of the tasks and task_history tables, for example: last_updated, mapping_editors, validation_editors, tasks_mapped, tasks_validated, tasks_badimagery.

The update of those fields every time a task action happens can be a cause for the database overloads problems we have. I'm not a database specialist, so I would like to have other opinions if a different database model or getting those informations from the tasks and task_history tables could make TM work better when there is a massive simultaneous activity on the same project.

[willemarcel]

It's also updating the User model with information like projectsMapped, tasksMapped, tasksValidated each time a task is updated.

We are not using that information from the user model on the frontend, so we should thinking about removing those fields from the User model