Whereas call integration (true self managed) sometimes is blacklisted.

Shouldn't be needed... but just in case, better than a crash

Seen in the wild at this location for "scheme not found" bad URI in here somehow

Too much sports metaphor

Can't get them to have icons for some reason...

Since sometimes there are transient failures, so if DNSSEC is present
and not validating try again before giving up

Upstream must have removed this...

I thought it had been enabled on both sides but at least make it the same.

If they didn't pick a specific message but report the whole chat as
spam, most recent message is spam.

This reverts commit d50fca4b912b8ef2b2ee9645986fbcd25d73dee9.

but it's just a temp file so we can't keep it

The call integration depends on the operating system giving us a list of
possible output devices (speaker, earpiece, BT headset, ...) via a
callback called
`onAvailableCallEndpointsChanged()` that is called as soon as the app
registers the call with the operating system.
For outgoing calls on Android 15 this method is no longer invoked
leaving Conversations without knowledge about what devices are available
and thus without the ability to switch between speaker and earpiece.

Logcat output seems to indicate that there might be some sort of race
condition (there is a line that says something like: available endpoints
changed but service was not bound)
There is further evidence in that if one tries multiple calls in a row
(10+) one might actually see the output device switcher / indicator.

However after a full day of investigation it seems that the race
condition is in the platform code; not in Conversations.

To not leak the quoted message

duh