The previous changes didn't work when we output a character +
deadkey. In response to outputting the character we get a
`ibus_keyman_engine_set_surrounding_text` call in which we
called `reset_context` which removed the deadkey marker. This change
fixes this problem by comparing the surrounding text with the
context we already have. Only if it's different we reset the
context.

- adjust indentation of `reset_context`
- move variable definition to block where they're used
- make use of method to detect surrounding text support

This change always gets the context from the surrounding text
if `reset_context` gets called. This helps when the user puts the
IP after a certain character. Previously we basically lost the
context, with this change we restore the context so that it's like
the user just typed the previous characters.

auto: increment master version to 16.0.79

chore(linux): Add Node.js to the docker container

fix(linux): Fix make install

Several fixes for building and installing locally.

Fixes #7397. Closes #7398. Closes #7400.

This change adds separate READMEs for the legacy projects, and
removes mentioning of the legacy projects in the current READMEs.
The motivation is to make it later easier to remove the legacy
projects, as well as reducing the efforts to testing the README with
legacy projects. Since legacy projects aren't maintained anymore
it doesn't make sense to still have them in the regular README,
suggesting that the instructions work for the legacy projects as
well.

- used in feature-ldml

Relates to #7102

[VSCode dev containers](https://code.visualstudio.com/docs/remote/containers)
allows to develop in a container and is configured through files
in `.devcontainer`. However, that directory falls in the same
category as `.vscode` in that it might be different on each
developer's machine, depending on preference and platform he's
working on. Therefore we exclude this directory similar to
`.vscode`.

fix(linux): Fix reordering of output

Co-authored-by: Marc Durdin <marc@durdin.net>

Only send fake event if client does not support surrounding text.

We forward a fake event for both keydown and keyup. This change
will set the flag on the fake event so that we get keydown and keyup.
This is probably not technically necessary, but it helps in
debugging because you can then see that both fake events still
belong to the same keypress.

If we're dealing with an older ibus version that doesn't have the
necessary patches we fall back to the old behaviour. Otherwise
we use the new output reordering.

This change implements a commit queue which allows to control the
order of the output. This ensures that any backspace we generate
will be processed before the character we're adding.

Requires changes in ibus (surrounding text fix (see #7072) and
prefilter change)

Fixes #1489, #4028, #4029, #4030, #4505, #5510, #6639

auto: increment master version to 16.0.78

chore(web): unit test polishing pass

fix(web): possible error on change of context to a contextEditable

auto: increment master version to 16.0.77

chore(linux): Cleanup unnecessary surrogate check

auto: increment master version to 16.0.76

chore(common): builder script maintenance

auto: increment master version to 16.0.75

Previously `process_unicode_char_action` checked for
`action_item->character` being a surrogate. This should never happen
because `action_item->character` is a 32-bit character. This change
removes the unnecessary check and the `keyman->firstsurrogate` field.

Fixes #6385.

fix(android/engine): Dismiss subkeys on multi-touch

chore(android/engine): Display Toast notifications on Sentry errors

auto: increment master version to 16.0.74