Add updateProject GraphQL mutation

[williamjallen]

This commit adds an updateProject mutation which will form the basis for the overhaul of the project settings page. Note that our infrastructure doesn't support multi-part GraphQL requests yet, so I plan to create a separate dedicated route for project logo uploads, outside the GraphQL API.

[josephsnyder]

Most things look and respond great to the mutation running in GraphQL Explorer. My only question is:

Should we allow name in the mutation? If they had access to the settings page for the project, they wouldn't be able to change the name. It is validating properly for name collisions still so they can't collide.

[williamjallen]

@josephsnyder Based on the feedback we got last year when projects wanted to change names due to the case-insensitivity change with the MySQL->Postgres transition, I figured that it's an important thing to have. I wouldn't be opposed to disallowing name changes if you have a good argument for that though.

The tests for name changes are here.

[josephsnyder]

if you have a good argument for that though.

I wouldn't say its a good argument, just noticing it's something we don't currently allow. The case-insensitivity makes sense. Thanks @williamjallen