At least show them as a private message from the room, implement full
form-in-message flow later

* 'master' of https://codeberg.org/iNPUTmice/Conversations: (134 commits)
  Translated using Weblate (German)
  Translated using Weblate (Galician)
  version bump to 2.12.6 + changelog
  add CI via woodpecker
  Translated using Weblate (Galician)
  Translated using Weblate (German)
  Translated using Weblate (Vietnamese)
  Translated using Weblate (Vietnamese)
  add ј to list
  q is not cyrillic but ԛ and х are
  version bump to 2.12.5 + changelog
  Translated using Weblate (Vietnamese)
  Use libidn for stringprep
  UP: add custom extensions for app<->distributor interaction
  process stream features after success when we inlined bind but not sm
  Translated using Weblate (Vietnamese)
  Translated using Weblate (Swedish)
  Translated using Weblate (French)
  Translated using Weblate (French)
  Translated using Weblate (Czech)
  ...

Currently translated at 100.0% (48 of 48 strings)

Translation: Conversations/App Store Metadata
Translate-URL: https://translate.codeberg.org/projects/conversations/app-store-metadata/de/

Currently translated at 4.2% (2 of 47 strings)

Translation: Conversations/App Store Metadata
Translate-URL: https://translate.codeberg.org/projects/conversations/app-store-metadata/gl/

Otherwise every UI refresh of any kind causes text boxes to lose focus.

Do not show "none" affiliation since it doesn't really mean much and is
the default, same for "participant".  Show "visitor" role as "muted".

Hats are coloured by the URI not their name.

based on docker image provided by Gadgetbridge

focus for now is getting something build. we can optimize this later and
provide our own image

Currently translated at 4.2% (2 of 47 strings)

Translation: Conversations/App Store Metadata
Translate-URL: https://translate.codeberg.org/projects/conversations/app-store-metadata/gl/

Some servers ignore extra payloads on the change presence itself, so once that's
done then send the extra payloads in a new presence.

Which was causing a crash here.

Currently translated at 100.0% (47 of 47 strings)

Translation: Conversations/App Store Metadata
Translate-URL: https://translate.codeberg.org/projects/conversations/app-store-metadata/de/

Currently translated at 100.0% (13 of 13 strings)

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

Currently translated at 99.8% (965 of 966 strings)

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

This requires not compressing it or cropping it unless we want to do *a lot*
more code, so file must be under 100k or we freeze it and no promises what your
non-square avatars will look like generally.

All drawables forever

Currently translated at 99.8% (965 of 966 strings)

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

Which actually validates according to spec instead of just being lazy.

On registration the app can pass in a 'Messenger' to get a direct response
instead of having to somehow wait for the broadcast receiver to fire.

The app name can be passed as a pending intent which allows the distributor
to validate the sender.

Serious UI lag and bugs when it gets too big

See https://soprani.ca/todo/302

Some things are banned by resourceprep that a user might wish to use.

If this happens, then punycode the resource so they can at least join the room.
Always send their chosen nick (not a mangled version) as <nick> in presence.
Always save their chosen nick (not a mangled version) in bookmarks (risky, since
if they try to use this bookmark from a client not supporting this it may not
let them join without changing nick).
If we get a <nick> in presence, then we respect it if it matches the punycode
decode of the resource (this is to prevent spoofing or double-naming since MUC
services won't be validating the <nick> at all right now. May relax this in the
future).
Save their actual nick (whatever we're actually showing, so <nick> if we used
that) into conversation attributes instead of assuming it will match the
resource.
Use resource for technical stuff (like PM addressing) and nick for display.

Hilight on both nick and resource so that mentions from legacy clients work.