To make services easier to find

* tag '2.12.1': (43 commits)
  version bump to 2.12.1
  Translated using Weblate (Galician)
  Translated using Weblate (Spanish)
  Added translation using Weblate (Albanian)
  Added translation using Weblate (Albanian)
  UP: null check transport verification
  version bump to 2.12.0
  Translated using Weblate (German)
  Translated using Weblate (Polish)
  Translated using Weblate (Polish)
  Translated using Weblate (Romanian)
  Translated using Weblate (Polish)
  Translated using Weblate (Russian)
  Translated using Weblate (Polish)
  Translated using Weblate (Romanian)
  add changelog ahead of release to allow translation
  version bump to 2.12.0-beta
  Translated using Weblate (Spanish)
  Translated using Weblate (Spanish)
  Translated using Weblate (Polish)
  ...

* add-after-register:
  Make sure command intent can work even if we don't have caps for the jid
  Add roster item after registering with a service

Currently translated at 100.0% (962 of 962 strings)

Translation: Conversations/Android App (shared)
Translate-URL: https://translate.codeberg.org/projects/conversations/android-app-shared/gl/

* debug:
  Support API 33 feature detection

* true-from:
  Support for XEP-0428 v0.2.0
  Support extended addressing ofrom when domain matches

Store `fallback` elements in payloads.  If there is a `fallback` for something
we support (currently extended addressing and oob) then use the data provided to
snip the relevant portion out of the body.

Generate `fallback` element for oob we send, since we do send a fallback body.

Allow a message to appear as from a different jid using ofrom if the domain
matches the actual from and source domain advertises support for extended
addressing. This is safe because spoofing control is up to the source server,
and the source server could have chosen to write a different from with the same
domain if it wished.

If there is a true counterpart (set from ofrom) then display nickname like in a
MUC because this message isn't from the normal counterpart of this conversation.

* sims2:
  If we already have a file by this hash, let's just use it
  Helper to get Cids for the <hash> elements
  Helper to get file element, where thumnails etc live
  Don't just start from blank if there are some FileParams we can update
  Support BoB thumbnails
  Support android Uri as well as java URI
  Support data-uri thumbnails
  Show thumbnail during download, if relevant
  Show fallback thumbnail if there is no image
  Helper to get thumbnails from SIMS element
  Store FileParams as SIMS in payloads
  Prevent accidental mutation of Elements
  Parse all SIMS and OOBs on a message

Currently translated at 100.0% (9 of 9 strings)

Translation: Conversations/Android App (Quicksy)
Translate-URL: https://translate.codeberg.org/projects/conversations/android-app-quicksy/es/

Was already the case for BobTransfer, but here we do it before looking to see
what kind of transfers are supported.  Even if there are no sources at all, if
we have this has already it'll work.

Some thumbnails are just as good as scaling down the real image, but
some (especially blurhash) are not.  So if nothing that's "good enough" to go in
the main cache is present, try the fallback.

If there is a thumbnail we can render right now (as of this commit, just
blurhash) then render that alongside the download button.  Tapping the image
starts the download just like the button.

We no longer use the old fileParams column or serialization format for new
messages, instead storing and loading to/from a SIMS element in payloads.  If
the incoming message had a SIMS element, we preserve it as much as possible and
only add newly discovered information to it.  If the incoming message had a
different kind of attachment (such as OOB) then we synthesize a SIMS element
from the extracted data.

SIMS has no spec for storing width/heigh/duration of the final media, so use RDF
namespace from schema.org for those data.

If you want to mutate, use bindTo and mutate the Element, don't getChildren()
and mutate that or it will get out of sync with childNodes

Use a set that keys on URL so that we don't get duplicates.

Still only store the first one for now.

And make sure once it comes "online" for us that we refresh command list, if relevant.

* threads:
  When locked, just unlock
  Update default thread on scroll explicitly
  Set thread from attachments and direct reply
  Option to lock a specific thread
  Tap message bubble to set thread
  Long press to clear thread
  Prevent thread from changing after user selects manually
  Show thread marker, send thread in stanza, allow replying and starting new thread
  Show identicon for thread when present
  Store thread data on incoming messages

(direct reply is reply to a specific message in a notification)