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

closes #4071

This is used when something goes wrong with a MUC, e.g. a connection
error made the MUC kick you out. In this case you generally want to try
to rejoin.

* 'muc-kicked-technical-reasons' of https://github.com/Zash/Conversations:
  Add handling of status code 333

Show chatrooms and contacts together in one list and search searches both of them.

* 'feature/missed_call_notifications' of https://github.com/dmitry-markin/Conversations:
  Fix: show missed call notification if ringing timeout is reached
  Add missed call notification icon
  Missed call notifications

* github.com:iNPUTmice/Conversations:
  Change string format
  Add timestamp for all calls

* 'alwaysbatterydeopt' of https://github.com/licaon-kter/Conversations:
  Here too
  Show battery dialogue always

this only causes race conditions

Uses phone location and libphonenumber to normalize.

Rather than starting right at dialling, which seemed to cause sometimes delays
in the in call screen appearing and also a different behaviour when a post dial
string was present, passing through all the states with some time in between
seems to result in a more stable and consistent UX with no change to functionality.

* more-tags:
  Default dynamic tags to on
  Display phone number type/label as a tag where relevant
  Show dynamic tag "Android" when item is in Android contacts only

* dialler-integration-permissions:
  Ask user for microphone permission from dialler integration

* gateway-icon:
  Show gateway avatar on in call screen

We can't ask them for it directly.  The library I am using here will first check
if the permission is already granted.  If so onPermissionGranted will fire and
we will start the call.  If not, the Connection will be created in a dialling
state and a notification will appear saying that the app needs additional
permissions.

Once the user taps the notification they will then be asked to allow microphone
access.  If they say yes, the call will proceed.  If they deny, the call will terminate.

* pstn-gateway-can-call:
  PSTN gateways contacts can do voice calls

* sync-tel-contacts:
  Sync system contacts by phone number

* dialer-integration-2:
  Mostly rewrite dialler integration
  Much prettier calling account

Using the same logic as Quicksy, but not submitting to an API just assume that
tel@pstn-or-sms-gateway is a valid Jabber ID.

Does not add to roster or reveal presence or send anything to a server, just
affects local UI.