implement easier API key setup

[jacobvenable]

Below are various API keys needed to enable features in the provider portal. This issue seeks to either implement a technical enhancement that makes setting them up easier, and/or formalizing a process for developers to follow in retrieving API keys.

OAuth Logins

This is not a requirement of running the provider portal; however, most valuable features require logging in which is currently only possible through OAuth logins (Facebook, Google, or Slack). The only requirement for these functioning are providing proper API keys in the server's environment file.

Algolia

This is a not a requirement of running the provider portal; it is only a requirement to perform any resource searching locally.

The only requirement for these functioning are providing proper API keys in the server's environment file.

Open Weather API

This is a not a requirement of running the provider portal; it is only a requirement to hit our weather endpoint that caches calls to the Open Weather API.

The only requirement for these functioning are providing proper API keys in the server's environment file.

[jollyjerr]

It would be nice if we could come up with a good solution for this. Would a private slack channel be secure enough? If not - we could have an invite-only google doc or something?