Since https://github.com/mroonga/mroonga/commit/35f593037c2d8f5a497349ff98f3a3ce31ee95de
install.sql has been split in install.sql and update.sql, adjust the
script to source both.

install.sql only contains INSTALL PLUGIN, it's safe to run it on every
update (that's what we always did).

This fixes a regression that mroonga user functions were no longer
available after d0589a41 (version up: MariaDB 10.3.35/10.4.25, groonga
12.0.4, mroonga 12.04, groonga-normalizer-mysql 1.1.8, 2022-06-10)

Thanks to migration to json-in-xml serialisation some lower level bugs has
been discovered with value types in the profiles, so simply fix it.

default and kvm-cluster software types are now json-in-xml, so they accept
and return json-in-xml.

Update tests to show that xml and json-in-xml serialization works.

Note: There was invective to publish with pure XML serialisation, but it is
wrong idea because:

 1) serialisation in the software.cfg.json is provided for both ways
 2) requesting instances with given serialisation by profiles expect same
    serialisation

Request resilient instances with serialised, as they reply with json-in-xml.

Fixes this warning when running test:

    UserWarning: Error validating request parameters against schema definition:
    RefResolutionError unknown url type: 'instance-input-schema.json'

jsonschema (the python library) support this kind of refs when using
version draft-06 but not when using draft-04.

json-language-features (from theia text editor) does not understands
file.json#/ references, it complains:

    $ref '/' in 'file://...' can not be resolved.(768)

but not using the trailing / works fine

b'💥' is a SyntaxError in python.

Instead, switch to accessing options from option variable and apply
this to other options from this part.

This fixes this issue:

    While:
      Installing switch-softwaretype.
      Installing favicon.ico.

    An internal error occurred due to a bug in either zc.buildout or in a
    recipe being used:
    Traceback (most recent call last):
      File "zc.buildout-2.7.1+slapos019-py3.7.egg/zc/buildout/buildout.py", line 2360, in main
        getattr(buildout, command)(args)
      File "zc.buildout-2.7.1+slapos019-py3.7.egg/zc/buildout/buildout.py", line 640, in install
        self._install_parts(install_args)
      File "zc.buildout-2.7.1+slapos019-py3.7.egg/zc/buildout/buildout.py", line 820, in _install_parts
        installed_files = self[part]._call(recipe.install)
      File "zc.buildout-2.7.1+slapos019-py3.7.egg/zc/buildout/buildout.py", line 1668, in _call
        return f()
      File "slapos.cookbook-1.0.244-py3.7.egg/slapos/recipe/switch_softwaretype.py", line 108, in install
        sub_buildout.install([])
      File "zc.buildout-2.7.1+slapos019-py3.7.egg/zc/buildout/buildout.py", line 640, in install
        self._install_parts(install_args)
      File "zc.buildout-2.7.1+slapos019-py3.7.egg/zc/buildout/buildout.py", line 820, in _install_parts
        installed_files = self[part]._call(recipe.install)
      File "zc.buildout-2.7.1+slapos019-py3.7.egg/zc/buildout/buildout.py", line 1668, in _call
        return f()
      File "slapos.recipe.build-0.54-py3.7.egg/slapos/recipe/build/__init__.py", line 268, in install
        return self._shared.install(self.__install)
      File "slapos.recipe.build-0.54-py3.7.egg/slapos/recipe/__init__.py", line 150, in install
        install()
      File "slapos.recipe.build-0.54-py3.7.egg/slapos/recipe/build/__init__.py", line 278, in __install
        self._exec(self._install)
      File "slapos.recipe.build-0.54-py3.7.egg/slapos/recipe/build/__init__.py", line 261, in _exec
        code = compile(script, self.name, 'exec')
      File "favicon.ico", line 6
    SyntaxError: bytes can only contain ASCII literal characters.

See merge request nexedi/slapos!1183

See merge request nexedi/slapos!1177

`depends = {slapos-cookbook:recipe}` bug when `virtual-env-base` is used in an instance.cfg.

Now, `virtual-env.cfg` will create an instance by default.

This instance will publish `activate` script path.

This fixes 92130619 formatting.

erp5.recipe.w3validator is not installed, it was just a version pin
because when running buildout updating the software needs a version
pin, by now all softwares must have been updated.

These tests are still using `python setup.py test` which installs
missing packages to their latest versions. Recently, certifi (a
requests dependency) published a new release with python3 only
syntax, so running the test now got an error installing missing
packages:

    File "parts/slapos-package/playbook/roles/standalone-shared/.eggs/certifi-2022.5.18.1-py2.7.egg/certifi/core.py", line 17
        def where() -> str:
                    ^
    SyntaxError: invalid syntax

The `playbook/roles/standalone-shared` is defined on the test suite
as instance parameters, so it seems we can not already install this
package directly from playbook/roles/standalone-shared because
test suite may define something different. For now, just install
requests. All this will have to be addressed when we change this
test to pre-install packages with slapos and use `python -m unittest`
instead of `python setup.py test`.

These two options were unusable for software releases using python3.

This also adds test coverage for the recipe.

These are not supposed to be executed directly

See merge request nexedi/slapos!1179

This reverts commit 4fa33dfc.

This patch is not complete, backporting full support of
`__{code,defaults}__` on Zope2 would require patching more, so we
decided to keep using func_code with ERP5 on Zope2 and to use
__code__ only with ERP5 on Zope4

Extend the upgrade tests to create data before the upgrade, to
confirm that this data can still be found after the upgrade.

This also extends the test to confirm that after upgrade, inituser
can still login, create content and find content created before and
after upgrade.

After 4fa33dfc (erp5: py3: `func_{code,defaults}` was replaced in
Python3 by `__{code,defaults}__`., 2022-04-25), this was no longer
the case, because during indexation, using existing scripts failed
with AttributeError __code__

There is no real control over port chosen by push/pull.