Allow an admin to create a new project

[wasade]

As the subject says. This PR also scopes to denote whether is project is to be considered a microsetta project.

[dhakim87]

Yes qa! What exception does it throw? You can take the unique constraint violation code out of the other repo classes.

[dhakim87]

Also, wrapping psycopg2 errors in RepoException and re-throwing them in the repo layer will automatically trigger 422s to be returned, which is convenient when you need to specify an error message close to the source

[wasade]

Ah okay so dont need to wrap this business in a try/except then right?

[dhakim87]

If its specifically a RepoException, it will turn into a 422 from the registered handler in server.py. If its a different type of exception underneath, it'll do whatever is registered, or 500. That lets you 404 from the repo layer with NotFound or throw 422s with RepoException. You still have to catch the psycopg2 unique violations explicitly, but I do that at the repo layer and reraise them as RepoExceptions usually.

[dhakim87]

Why VARCHAR with Yes/No rather than the Postgres BOOLEAN type? Then we wouldn't need to think about capitalization, which has burned us in a previous "Yes/no" field.

[wasade]

Not an issue, happy to address

[dhakim87]

I really dislike the is_microsetta Yes/No field without further justification. I'd much prefer either a boolean or renaming to "microsetta" and explicitly enumerating all possible values. Whether or not the 422s are fired from exceptions is totally optional.