Merge develop-2.x into develop

[IMPROVEMENT] Only allow Openable content in Storage Access Framework

Merging develop 2.x into develop

[FIX] App build.

Add the CATEGORY_OPENABLE to the Intent to launch the Storage Access Framework (SAF) when sending a file. Setting this category ensures that the OpenableColumns data contract is met by the opened data, which we rely upon during data upload.

In practice, some content, such as Contacts, will no longer display in the SAF UI.

Fixes #935

Remove the request for READ_EXTERNAL_STORAGE permission

Capitalize socket connection status strings

We use the Storage Access Framework (SAF) to enable users to send files. When using the SAF, READ_EXTERNAL_STORAGE permission is not needed to read from internal storage, SD Cards, or anything else. The Android System is the one accessing the storage, so applications do not need direct access. This is in fact one of the major selling points of the SAF.

Note that no Google samples or apps by Google Developer Advocates that highlight the SAF request this permission.

Removing this permission is a good thing. Firstly, there are many SAF providers such as Google Drive, Photos, Microsoft OneDrive, etc, that do not use external storage. Secondly, users are not prompted for a needless permission. Thirdly, it reduces the complexity of the ChatRoomFragment.

These strings are displayed to users, and accordingly, should be match the capitalization of other text.

[DOCS] Improve a little bit our issue template

[NEW] Facebook oauth login

[CHORE] Prepare the app to hotfix 2.0.2

[FIX] Fixes for the 2.0.2 hotfix

[FIX] Fixes for 2.0.1

[HOTFIX] Move version check to server screen

We need to see how to better handle it.

[FIX] Fixes for 2.0.0

https://fabric.io/rocketchat3/android/apps/chat.rocket.android/issues/5ad550c336c7b23527f80a02/sessions/latest

Explicitely use Application context

[RELEASE] Prepare the app for final 2.0.0 release