Need to address multiple flavors working with google-services.json

[atsakiridis]

Impacts:

• See if we need to have separate server side applicationId, for each of the application ids we want to support. Also brainstorm how to best make this work
• Together with that better to use globally same organization in firebase backend and have separate users under telestax org
• Make sure that we don't expose google-services.json sensitive information

The problem right now is that the id is the same and as a result developers after release just overwrite the released apk with the debug one currently developing. This means that devs don't really stay long enough actually using the production .apk and lose touch with it. Another downside until we fix contacts in the server side is that we lose the numbers too.

To address this let's consider using a debug/dev applicationId and in CI we just set applicationId to the production one. That way production .apk is left side by side with development.

Let's also use a watermarked icon for the 'debug' one. @ognjenns I already have the icon ready, so let me know when you are ready so that I provide it to you

[atsakiridis]

Let's also take the opportunity to update telestax owned project

[atsakiridis]

Here's a list of more detailed impacts for future reference:

• Update build configuration to build debug using .debug prefix
• In Firebase Console create additional App in our Olympus Project using the .debug prefix and update google-services.json including 2 clients, one for each App. See if this will work or if we need to add separate google-services.json in the source-sets.
• Create release signing configuration, by generating new keystore, etc. Make sure that the sensitive details aren't shared in the repo
• Create separate graphics for mipmap for debug, but using a new debug source-set
• Don't forget to update to using corporate Firebase project
• Don't forget to also address .premium & community applicationId. In the end we want to have 4 combinations: community-debug, community-release, premium-debug and premium-release. These need to be reflected in Firebase console as well and finally we want the .apk naming to be clear, as well as Application name to be easily found in the device.
• Remove TestFairy facilities from debug builds. They add a lot of noise and we don't really care about stats for local builds that we can examine anyways via android studio debugging facilities
• Update .travis.yml configuration for Oreo which is breaking
• Update gradle wrapper for SDK that is breaking