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

Instead save a very small object with the string in it and draw every
time. Drawing a single letter is not noticibly slower than blitting a
bitmap of the same size. It may even be faster, and certainly saves RAM.

By computing same size for messages and for overview

But may delay by more than the interval this way

If it's constantly evicting things, that's bad for performance too.

Otherwise if one is disabled we bail out of call integration and lose features.

And don't pass over for sortedTime or else sorting the list takes way
too long.

Show only the added emoji and nothing on removal