Adding support for multiple communities

[probablyangg]

Pushed in changes required to support multiple communities on convo.cafe

Breaking change:

• Each event must be associated with a Community -- meaning there's no "default" community. Right after merging with main we need to run a script that defaults all existing events to "kernel" community
• A community is identified by a subdomain (and subdomain only). No subdomain = defaults to "kernel" community
• We seed the database with 1 community, with id kernel, this will be the default fetch and store of events if no subdomain is found

Setup:

• We need to create a new subdomain for each community and add them to the database so the client recognises the subdomain name with the associated community
• Each community can have associated "services" - these are custom implementation of triggers associated with an event (eg., notify a slack channel after creation of an event, etc.)
  • we currently support two services: Google and Slack, both require manual admin setup (getting into the database)
  • For google, we'd require the community admin to provide read and write access to kernel's convo app for their google calendar so the app can create and update events on the shared calendar
  • We would need to update the subdomain redirect URI on the google console and in our database

[probablyangg]