Voice input / transcription

[AltanS]

Two PRs have now added speech input to the composer, from two different people:
#91 and
#115. Both were careful work. No issue has ever asked
for it, so people want this enough to just build it, and I am clearly missing something.

Collie's composer is a plain textarea, so your phone keyboard's own microphone already types into it
and the per-pane draft keeps the result. No setup, and on a modern phone it stays on the device. What
does that not give you? Reply with a number, or tell me what I left out.

1. The keyboard covers the pane output you are replying to.
2. You still have to tap Send. Not hands free.
3. Accuracy on identifiers, filenames, flags, command names.
4. It gives up on a pause, so long prompts get cut.
5. You have to speak the punctuation.
6. Your language, or mixing languages.
7. Not available to you: managed device, Siri off, a keyboard without it.
8. You are not on a phone. Desktop browsers have no keyboard microphone.
9. You would rather use a model you run yourself.

The two PRs point different ways. #91 keeps Send explicit and lets you point at your own endpoint.
#115 sends hands free by default. Those are not the same feature, and knowing which one people want
matters more than the code does.

What makes me hesitate is the machine running Collie picking up a credential, an outbound network
path, or a long-running child process in order to transcribe. That bridge binds to loopback and
manages one front door, and I would rather it stayed that shape. Doing it in the browser is one way
around that, but I am not claiming it is the only one. If there is an arrangement I have not thought
of, I would much rather hear it than have someone spend another weekend on a PR I decline.

Thanks to @en-ver and @ardaaltinors.