Feature/rest public tables

[RogerTangos]

• Public Repositories
  • Anonymous users can browse/search/query public repositories via the web interface
  • Authenticated users can browse/search/query via the web interface or the REST api
  • Cards can be marked public
• Public Cards
  • Anonymous/Authenticated users can execute saved queries (cards) through the web interface
  • Authenticated users can also execute cards through the REST api
  • Public cards are not discoverable at the moment. The (non-obfuscated) link must be shared with users
  • Queries in public cards are executed using the database role of the card creator. Whatever they see, others will see
• Permissions
  • Introduces a new has_file_permissions layer to manager
  • Allows finer grained access control for cards

[RogerTangos]

Note: when merging, migration 0015 should be renamed 0016. Public and anonymous roles are made automatically as part of the migration... but it's also possible to trigger them manually by typing python manage.py createpublicanonuser. This won't remove existing public/anon users, so there's really no harm in doing it.

[justinanderson]

Merging into master instead, per #137. feature/rest isn't ready.