Build org schema

The 'org' is either a incorporated entity, or an unincorporated entity, depending on the type of org, and should only have properties related to that. So far we only have 'org' name.

A lot of the other apps have a concept of an org which is only a small facet of the 'org', based on their limited data and scope. e.g. GCI and GSOC and OpenHub and any attempt at modelling GitHub/GitLab directly or via IGitt.

- org -> projects (coala, coala-bears, etc)
- org -> programs (GCI, GSOC, newcomer-onboarding, school outreach, thesis supervision, etc)
- org -> teams (https://github.com/coala/community/issues/12) -> people
- org -> services used -> Git hosters -> repositories
- org -> products -> PyPi releases

The one area I am a little grey about is whether we should have a strict 1-1 relationship between project & repository in our design & terminology. The biggest implementation violation of that is https://www.openhub.net/p/coala/, which was historically a dumping ground for all repos, and we should probably clean that up more.