Handle Default Owner

When a user with only 'edit own volunteer projects' and 'create volunteer projects' creates a new project the owner is unset. Then when the system attempts to set the owner, the user wont have permission. This is currently propped up by the fact that the volunteer_project_contact api isn't doing proper permission checks. This issue will need to be addressed in one of two ways before the permissions issue can be addressed.

1 (best): Encapsulate the relationships inside the call to project::save so that they are created from the outset. This will require some refactoring like was done with profiles.

2: Check the permissions for a user and if they do not have 'edit all volunteer projects' make them the owner of the project when they create it.