Move template data out of project into its own class

[hltcoe-bot]

Would be a one to one relationship between Project and Template. Motivation is that loading all the templates when displaying a list of projects is very inefficient. We could switch the loading code to select certain attributes to return as a dictionary but there is likely downstream code that expects to have fully hydrated Project objects. I think it is easier to move the template data out of the class so that it is only loaded when needed.

A side benefit is that this moves us a step closer to having a way to tracking which template was used for what batch/task as we could archive previous templates.

Poster: Cash Costello id: 204

[hltcoe-bot]

mentioned in issue #195

Poster: Cash Costello