Forgot this for incoming calls

* Fix a few potential errors due to the use of newer APIs (minSDK is
  still only 24)
* Fix one remaining case of raw usage of generic types.

For incoming calls, we fall back to the built-in call UI if the
microphone permission is not granted. The reason is that if the Dialer
UI is displayed over keyguard, then the user may not even be able to see
the notification that we show in order for them to grant the permission.
Having a small annoyance for the first incoming call is better than
having the in-call UI hang.

This makes 464XLAT networks (such as T-Mobile LTE) work.

https://bugs.chromium.org/p/webrtc/issues/detail?id=10707

Sometimes even in Conversations-to-Conversations I see symptoms like receiver
says 99% done, sender says 100% done, hangs like that and then file transfer
fails.

I was having this issue fairly reliably between my emulator and my test device.
Adding this close caused the transfer to succeed 100% of the time.  I'm not sure
why the receiver didn't read all the data properly without the close, but this
fixes it.

* jabber-iq-gateway2:
  Improve example hinting
  Move GONE/VISIBLE to the controller instead of the model
  Show identity category gateway even without jabber:iq:gateway prompt
  Sort gateways
  Switch to AndroidX LinearLayoutManager
  Parse phone numbers using local settings before asking gateway
  Try all gateway translations options
  Change input type based on gateway type
  Load gateways into UI
  Use a RecyclerView for list of gateway options
  Fetch jabber:iq:gateway prompt

Send jabber:iq:gateway if we're responding to that and fetch translated
response as the JID.  Otherwise use JID escaping if supported.
Otherwise fall back to the dumb ancient % escaping.

If there are no gateways in the current account's roster, just show the
old "Jabber ID" label.  Otherwise show a list of toggle buttons.  These
buttons show the type of their gateway and change the JID input to
not autocomplete and to show a hint matching the jabber:id:gateway
prompt.

This is just UI, submit behaviour is unchanged. List is not yet populated by
this code.

* manage-calling-accounts:
  Shortcuts to get to phone account settings screens

Helpful because they can be hard to find, and one or both of them is sometimes
straight up hidden on some ROMs.

* gif:
  Stop double caching the thumbnails
  Play animated gifs inline

Notification doesn't need it cached anyway, so save the space.

On Android 9 or above, older devices will fall back to the GIF overlay.

* unified-start-conversation:
  Unified Start Conversation activity

* image-attachments:
  Downloadable gets priority over emojis only
  Display both message body and media, where relevant
  Store oobUri and preserve message body

* upstream/master: (27 commits)
  show 'using account …' in incoming call screen
  show contact jid in call screen
  bump copyright year
  Add handling of status code 333
  increase default pw length
  do not build emoji flavors
  pulled translations from transifex
  add changelog
  fix ice candidate sending when different credentials are used
  remove security check that ensures rtp connection was properly finished
  code clean up
  bump agp
  store encrypted pgp files in private cache dir
  do not restart wakelock if activity is finishing
  delete pre lolipop weOwnFile()
  use try with resources. remove unused methods
  rename version suffix to playstore/free
  bump appcompat, migrate to emoji2 and get rid of emoji flavor
  fix rare npe
  store recordings and documents in their respective folders
  ...

This makes 464XLAT networks work.

https://bugs.chromium.org/p/webrtc/issues/detail?id=10707

Instead of assuming that body must contain the OOB URI if present, store it
independently.  Instead of overwriting the body with file metadata, store the
metadata in its own location.

* subject:
  Store and display message subject

Creates a new database for cheogram that is attached to the main connection so
that joins between the two can happen.  This allows us to migrate our DB schema
seperately from the Conversations schema to keep merging with upstream more realistic.

* dialler-integration-3:
  Unify phone number normalization with Quicksy
  Passing through initializing -> inititalized -> dialling more stable