Modify components to make them compatible with `slapos.recipe.cmmi` shared mode.

Most of them were straightforward, except:

 - aspell, where all dictionnaries parts were installed in aspell part. Instead of this, we generate an aspell wrapper for each language. This wrapper runs aspell with environment variables so that it loads dictionnaries from the language.
 - fonts, where all fonts were installed in the same `${buildout:parts-directory}/fonts/` folder and where just installing a font part had the side effect to make this font available to every application. Now each font is installed separately and it becomes applications responsability to generate a fontconfig's fonts.conf and set `FONTCONFIG_FILE` environment variable to load it, as described in https://www.freedesktop.org/software/fontconfig/fontconfig-user.html . A new `template-fonts-conf` section was introduced for this.
 - mariadb, where mroonga plugin write in mariadb's folder. For this, mroonga plugin is installed in another directory along with all original mariadb's plugin (that are copied) and mariadb service is configured to use mroonga's plugin folder instead of the default mariadb's folder.

See merge request !706

Include a slapos command implemented with slapos standalone

See merge request !743

don't add automatic route when adding IP address on interface because
the automatic route doesn't add "via XXXXXX" gateway option.

In KVM setup, the host machine is the gateway. We need to go through the
gateway because we can't reach directly the other VM running on
different slaptap interfaces.

As SOFTWARE_HOME is added at the top of sys.path, this meant that Zope2.egg/Zope2
ended up at the top of sys.path:
  * This broke `imp.find_module('App')` and Pylint (`No name 'Extensions' in
    module 'App' (no-name-in-module)`) because there are `App` modules in both
    Zope2.egg/Zope2/ and Zope2.egg/ and the former was returned.
  * "Normal" instances and Products.ERP5Type.tests.runUnitTest properly set up
    SOFTWARE_HOME to Zope2.egg/.

Additionally, according to Zope2/Testing documentation, SOFTWARE_HOME is only
needed to find Zope2.egg/Testing module, already available as Zope2.egg is in
sys.path.

Mariadb was not shared, because installing mroonga writes a plugin in
mariadb's plugin dir and it's not allowed for one part to write in
another part's folder.

The approach is to install mroonga plugin in it's own plugin directory,
then copy all mariadb default plugins in this plugin directory and
configure instance to use mroonga's plugin directory.

Groonga also has plugins and we are using groonga-normalizer-mysql
plugin. Fortunately, groonga reads plugins located in paths listed in
GRN_PLUGINS_PATH environment variable, so we can use a simpler approach
of installing plugins in their own installation folder and set
GRN_PLUGINS_PATH in the environment of processes using groonga, ie. the
mariadb server process.

This test make sure that groonga-normalizer-mysql is functional

Users will need to generate a proper fonts.conf and set it as
$FONTCONFIG_FILE environment variable.

The recommended approach is now to generate a font.conf file using
slapos.recipe.template:jinja2 since font.conf now needs entries for all
directories containing fonts.

Instead of the previous approach which relied on a side effect of
installing *-fonts parts that would write in parts/fonts/ and make the
fonts automatically available to applications, use a new approach where
each part is "pure", without side effects.
To make the fonts available to applications, a fontconfig font.conf
listing all the parts with fonts needs to be generated and set as
$FONTCONFIG environment variable.

A template font.conf is included in component/fontconfig

We now need to refer to the part where the dictionnary was installed.

this allow to share aspell component. Users needs to install the part
with dictionnaries, ie. aspell-en-dictionary instead of simply aspell

apr and apr-util are now build separately. I'm not sure there was any
benefit with that approach of copying the directories inside apache
source tree before build.

Using extra modules, like apache-antiloris require to install apache in
non-shared mode.

This also removes apache-antiloris from cloudooo and erp5 stacks so that
they can use apache as shared. Even if the section was installed, this
was not used anywhere.

gowork include gcc's location, which can be /usr/bin when system gcc was
selected.

This is required, otherwise published URL in slapos master is `"None"`

This is required, otherwise published URL in slapos master is `"None"`

After trying to generate a random image ourselve with image magic with:

    ${imagemagick:location}/bin/convert -size 6x6 xc: +noise Random \( -clone 0 -flip \) -append \( -clone 0 -flop \) +append -scale 128x128 $${:location}

I gave up and just download an image from gravatar, but ignoring errors
if any to comply with the "instanciation should work offline" rule.

like webrunner is doing

for better experience in the terminal

and stop creating some useless directories

To remove GIT_EXEC_PATH from environment as this can break running
buildout with slapos.recipe.build:gitclone sections using an
incompatible git version

because python-language-server-requirements.txt contains a git URL

includes vsx registry and our resolution fixes

log accesses (the logrotate conf already exists for them), and
remove the pattern "<IfDefine Port>" which was used when this
apache conf was extended by the software's apache extending
the monitor stack