* 'master' of github.com:iNPUTmice/Conversations:
  bump version code
  remove footnote hint in translations
  catch two rare exceptions to fix crash
  version bump to 2.10.4 + changelog
  pulled translations from transifex
  remove hint about yearly fee for server
  fix ability to use GoogleMaps ShareLocationPlugin
  pulled translations from transifex
  version bump to 2.10.3 + changelog

needed on targetSDK >= 30 for microphone access. Without this, we cannot
access the microphone in dialer integration mode since we are not the
foreground app.

https://f-droid.org/en/docs/All_About_Descriptions_Graphics_and_Screenshots/

* 'master' of github.com:iNPUTmice/Conversations:
  pulled translations from transifex
  catch security exception when importing backup
  pulled translations from transifex
  bump libraries
  show jid only for incoming calls during ringing
  version bump to 2.10.3-beta.2
  Enable WebRTC-BindUsingInterfaceName/Enabled/
  pulled translations from transifex
  be smarter about what files can be deleted
  use libwebrtc m99
  allow deletion of all files

* fastlane:
  Screenshot add contact options speeddial
  startConversation screenshot
  Draft new full description
  Generate a screenshot with fastlane

* 'for-singpolyma' of https://gitea.angry.im/PeterCxy/cheogram:
  ConnectionService: handle disconnected state correctly
  ConnectionService: implement onReject()
  ConnectionService: miscellaneous fixes
  ConnectionService: Dialer UI integration for incoming calls
  ConnectionService: fix unchecked type assignments

onDisconnect() will only be called when the user manually requests a
disconnect. When the call is disconnected by the rtp connection itself,
the call won't be cleaned up and the system will be stuck in an in-call
state. Handle this correctly by moving the clean-up code to a close()
function, and calling that function instead when we disconnect.

Note that we cannot call the cleanup routine destroy() from the
onStateChanged() function, because it seems that this triggers a
deadlock somewhere down the line, probably in the calling
account-related telephony code. Doing a close() function mirrors what is
done in the default TelephonyConnection implementation for RIL-based
calls.

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.