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.

[RELEASE] Prepare the app for final 2.0.0 release

[NEW] Auth deep link

[NEW] ColorAttachment (need a better name)

https://rocket.chat/docs/developer-guides/deeplink/
supports both rocketchat://auth and https://go.rocket.chat/auth urls

[New] Added scroll view to profile

merge

[CHORE] Increment version code to 2.0.0-rc1

Revert "[NEW] ColorAttachment (need a better name)"

[NEW] ColorAttachment (need a better name)

[IMPROVEMENT] Offline message sending support

[FIX] Fix more login options

[PROJECT] Change SDK imports.