Enable per-user access control on Task objects

* "Per-user" instead of "per-context" because Tasks may contain
  information from a context that one user can see, but another user
  cannot
* Add `user` parameter to `create_task`, and ensure `modified_by_id` is
  set on new Task objects
* Add permissions to `ProgramBasicReader`, `AuditorReader`, and
  `ObjectEditor` to `Task` objects using the condition that
  `modified_by` attribute matches the requesting user
* Add implication for `ProgramReader`, `ProgramEditor`, and
  `ProgramOwner` to `ProgramBasicReader` in the "common" context
Explicitly avoid "static-dot-" assets prefix in development

* E.g., even if using "development" and "app_engine" settings modules,
  we shouldn't use the "static-dot-" prefix.  This should fix a common
  issue with using `launch_gae_ggrc`.
Merge pull request #1119 from reciprocity/feature/fix-task-permissions

Enable per-user access control on Task objects