v0.18.2

A fix for clicks not reaching tabs drawn with Edge's engine.

Clicks reach WebView2 tabs every time

In a tab drawn with Edge's engine (Google Messages, or any tab switched with
Draw with Edge's engine (WebView2)), clicks could stop working after you
had used another tab and come back: nothing in the page could be selected
until you switched away and back again. An invisible part of Jackdaw's own
window was being placed over the tab and taking the clicks. The tab now puts
itself back on top as soon as that happens.

---

Unsigned build. Windows SmartScreen will warn on first run:
choose More info -> Run anyway.

Nothing else to install. The Signal tab drives a real
signal-cli process, and both it and the Java runtime it needs ship
inside the app -- so Signal works on a machine that has neither.
That is most of the download size.

Signal links this machine as a secondary device by QR. As with every
linked device, existing conversations do not arrive by linking: the
tab starts empty and fills as messages arrive, and contacts and groups
do sync. To bring older messages over, use Import history from a
phone in the Signal sidebar, which reads a backup made in Signal on
the phone.

Linux: install the .deb on Debian or Ubuntu -- it is the one
most people want, and unlike the AppImage it does not need libfuse2,
which Ubuntu has not shipped by default since 22.04. The rpm and
pacman packages are built on Ubuntu but target Fedora and Arch. The
AppImage suits anything else, given libfuse2.