IMS and MME are in the same instance, but there is only one TUN
per instance. IMS is not crucial right now so we temporarily remove it
until we implement a clean solution.

We were trying to patchelf a file that apparently exists when Theia
is compiled on Debian 8, 10 and 11, but not on Debian 9.

See merge request !1105

Include the hash of all parameters related to the embedded instance
as a comment in the standalone script, so that if the hash changes,
the script and its own hash change as well, and standalone service
will be restarted.

Generate standalone script in instance-theia.cfg.jinja.in instead of
in software.cfg, avoiding the need to forward all the parameters.

Include the hash of the relevant parameters in the abstract socket path,
so that when changing these instance parameters the promise waits until
the standalone service has taken the new parameters into account.

Change "Embedded Instance" to "embedded_instance", and rename existing
"Embdded Instance" into "embedded_instance" for compatibility.

Installing will setup git hooks, so we can do one step further and
also configure the mergetool

otherwise curl uses system ca-certificates if the system package is
installed and otherwise is not able to verify server certificates,
usually being observed in slapos as git refusing to clone with error:
SSL certificate problem: unable to get local issuer certificate

See merge request nexedi/slapos!1103

On Debian 9, the given rpath seem to be ignored when compiling
the `keytar` dependency of theia, for unknown reasons.

- Move [theia] section and dependencies into component/theia
- Make [theia] section shared

This was missing in this software and in 03c5b311 (Stop using
hexagonit.recipe.download, 2021-12-03) the hash got out of sync

also mention automatic installation method

Since https://github.com/eclipse-theia/theia/pull/10343 theia depend on
nodejs >= 12 and they test on 12 and 14. Use 14 to have an officially
tested version.

This removes the strong requirement to have python2.7 in theia, so we
just use the software python, which might be python3

https://github.com/metabase/metabase/releases/tag/v0.41.4

We observed some test failures like for example 1 where this assertion
was failing because message is `Error reading SSH protocol banner`.

Because the purpose of this specific test is to check that log rotation
of ban log work as expected and because we test more thoroughly the
ban itself in TestBan.test_client_are_banned_after_5_wrong_passwords, we
can simplify this test by just asserting that connection was refused, by
expecting a general exception. We don't care about the details of the
exception here.

After a ban, the first connection attemps seem to always be refused with
"Connection reset by peer" and that's why we did not observed failures
with TestBan.test_client_are_banned_after_5_wrong_passwords

[1]: https://nexedijs.erp5.net/#/test_result_module/20211208-1520AC26C/21

Fix the following build failure in nxdtest's own test:

    [2021-12-10 15:57:15,142] INFO     While:
    [2021-12-10 15:57:15,142] INFO       Installing.
    [2021-12-10 15:57:15,142] INFO       Getting section python-interpreter.
    [2021-12-10 15:57:15,142] INFO       Initializing section python-interpreter.
    [2021-12-10 15:57:15,142] INFO       Getting option python-interpreter:eggs.
    [2021-12-10 15:57:15,142] INFO       Getting section nxdtest.
    [2021-12-10 15:57:15,142] INFO       Initializing section nxdtest.
    [2021-12-10 15:57:15,142] INFO       Getting option nxdtest:eggs.
    [2021-12-10 15:57:15,142] INFO       Getting section .nxdtest.pyexe.
    [2021-12-10 15:57:15,142] INFO       Initializing section .nxdtest.pyexe.
    [2021-12-10 15:57:15,142] INFO       Getting option .nxdtest.pyexe:eggs.
    [2021-12-10 15:57:15,142] INFO       Getting option nxdtest:eggs.
    [2021-12-10 15:57:15,142] INFO       Getting option .nxdtest.pyexe:eggs.
    [2021-12-10 15:57:15,142] INFO     Error: Circular reference in substitutions.

This is hot, not a proper, fix to recover nxdtest.UnitTest-Master status.
I will think more calmly what to properly do.

If we enter user namespace via regular unshare without help from SUID
newuidmap/newgidmap, all supplementary groups are mapped to -1. As the result
when Go test tries to chown to a supplementary group, it gets EINVAL:

https://github.com/golang/go/issues/42525

-> work it around with patch to skip this chown tests.

A more proper, longer-term fix would be to fix Linux kernel to allow writes to
/proc/self/gid_map to setup mapping not only to original gid, but to all
original supplementary groups as well here:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/kernel/user_namespace.c?id=v5.16-rc4-0-g0fcfb00b28c0#n1143

this fix, even if accepted by upstream, would be long to be waited for to
propagate to distribution kernels that we currently use. So we go with this
workaround for now.

--------

Another patch is to fix the following TestSCMCredentials failure:

    === RUN   TestSCMCredentials
        creds_test.go:81: WriteMsgUnix failed with invalid argument, want EPERM
    --- FAIL: TestSCMCredentials (0.00s)

There the code tries to send uid0/gid0 credentials from non-zero uid and
expects EPERM reject from kernel. However under `unshare -Umc` uid0/gid0 are
not mapped to anywhere and so implicitly map to -1 and are rejected with EINVAL
by the kernel.

/reviewed-by @jerome
/reviewed-on nexedi/slapos!1095

4) Hook in python-prctl, as it becomes nxdtest dependency: see
   nexedi/nxdtest!13 (79d13eff)

/reviewed-by @jerome
/reviewed-on nexedi/slapos!1095