Adapt all promise sections to changes in plugin promise recipe.

Without this fix, selecting a completion with the keyboard is not really
possible.

In addition to update version of slapos.recipe.build, this fixes the
following misuse:
- init phase must only initialize the section, which implies no change
  on the file system
- init/install/update's slapos.recipe.build should not contain buildout
  substitutions (theoritically, there could be wrong escaping,
  e.g. ${buildout:directory} containing quotes)
These 2 points didn't not matter here but it gave a bad example
for anyone learning buildout.

With Theia 1.17.2 we remain stuck on the loading page.

This reverts commit 6103d29a.

This reverts commit a42d199a.

To have the timeline view

The issue is now fixed in 1.16.0

Eventhough our current pattern is not the most secure, we have no other
choice for now that to use such insecure patterns.

In https://erp5js.nexedi.net/#/bug_module/20210819-20614EE we track possible
improvements to this situation.

This new version has a dependency to libsecret

Also adjust dependencies to the ones from https://github.com/eclipse-theia/theia/blob/v1.16.0/examples/browser/package.json
except api-samples which is not useful.

Most tools work without this, but it's cleaner to define this anyway

Now that slapos-node-software service does not use --all we have to use another
approach for this test which re-installs an already installed software.

Use the slapos-node-software-all services which was made for similar use cases.

This introduces some breaking changes to the check_url_available
promise:

- http_code has been renamed to http-code
- check-secure = 1 has been deprecated; http-code = 401 should be used
  instead

also apply the change in software/theia/test/dummy/software.cfg for consistency

Change all `check_port_listening` promises to `check_socket_listening`
and rename all associated `config-hostname` arguments to `config-host`

Before this commit, instance parameters that have a default null value
in JSON format were rendered as 'None' string in instance-theia.cfg.

In particular, Theia frontends were always requested with unsolvable
SLA parameters that prevented a frontend from ever being allocated:
```
sla-instance_guid = None
```

This is required for example to preview images (ie. open a .png file from the
editor). Without the default value of {{uuid}}.mini-browser.{{hostname}} is used
but we don't have anything in place to resolve such domain names.

Before this commit, the Go workspace was always activated before
launching the Theia shell and starting the embedded supervisord.

This in turn added the gcc installed by Theia to the PATH, meaning
that nested instances would be compiled with Theia's gcc instead of
the system gcc, making the compilation outcome dependant on Theia.

With this commit, the gcc resolved by PATH is now the system one.

This option takes a string representing a valid JSON object and
forwards the corresponding python dict to the embedded instance.