Caddy's proxy stanza for defined path with spaces sometimes is working when
it's done like this:

  proxy /path with_spaces ip:port

It happens, that few first requests after starting Caddy it's working, but
then it fails with error message like:

  dial tcp: lookup with_spaces on ip: no such host

So to stabilise situation now paths are generated like:

  proxy "/path with_spaces" ip:port

ssl_proxy_ca_crt can be just empty value, and that's not acceptable.

Use @@LOCATION@@ template to provide proper prefix path.

These changes allow to build SlapOS on Debian Buster ppc64el.

The PowerPC 64-bits little endian platform appeared more recently into autoconf and therefore needed updated `config.sub` and `config.guess` files.

Somehow these only needed to be patched on autoconf itself which is quite dated (2012), and libyaml that does not ship it's own `config.sub` and `config.guess` files. Other components built fine out of the box.

`config.sub` and `config.guess` files were taken from Debian Buster itself. More information at: https://wiki.debian.org/AutoTools/autoconf

**This merge request would have to be backported to previous releases in the case components reference older releases of SlapOS, which, if I understand correctly, is the case some times.**

See merge request nexedi/slapos!780

autoconf and libyaml needed updated config.sub and config.guess files
on ppc64le.

gnu-config component was created to centralize updated config.sub and
config.guess files. autoconf and libyaml now extend gnu-config and
overwrite their bundled config.guess and config.sub with gnu-config's.

in the future, any component can extend gnu-config to update it's own
config.sub and config.guess files if necessary.

monitor app shows:

![monoring app showing /log url](/uploads/dbb22484f79ed1538a308c640d74c3dc/image.png)

but this URL can not be accessed:

![/log URL unauthorized](/uploads/cf74f2d8bb867123c39264d8f7d9de74/image.png)

The correct URL looks to be this:

![/share/private/log is OK](/uploads/4775d5d3841d8ffa68d67f2cf2b87b22/image.png)

See merge request nexedi/slapos!785

This MR includes the following steps:
1. Target Python 3
2. Upgrade powerdns from version 3.3.1 to version 4.2.1 --- which also means...
3. Rework the configuration to support the [new GeoIP backend config format](https://doc.powerdns.com/authoritative/backends/geoip.html)

See the commit messages for more detail.

Note: EDNS Client Subnet extension is enabled.

See merge request nexedi/slapos!764

With the recent powerdns upgrade, the GeoIP backend uses a new config
format, see zones-file.yml.jinja2.

zz.countries.nexedi.dk.rbldnsd (which maps IPs to countries) is replaced
by GeoLite2-Country.mmdb(1) (which maps IPs to countries & continents).

Note: zz.countries.nexedi.dk.rbldnsd is not deleted (yet?); it is parsed
to keep information about China and its IP ranges grouped by ISP.

cdn.conf.in (which maps RR(s) to countries) is dropped; it is replaced
by an equivalent mapping done inside zones-file.yml.jinja2.

Also, EDNS Client Subnet extension is enabled.

---
(1): Added in previous commit.

Note: Only boost>=1.35 and openssl are required to build powerdns from
source; ragel, bison and flex are also required if building from git.
See https://doc.powerdns.com/authoritative/appendices/compiling.html#dependencies

See merge request nexedi/slapos!781

Replace occurences of 2.7 version to:

 * just python part, in case if part was referred
 * to ${python:version} in case string was generated

In "Do not harcode version of wanted Python"
(3f930869) the references to pytohn are
dropped, but they are needed during OBS preparation.

Fixes:

 * switched to shared
 * used correct dependencies
 * fixed compilation parameters

Fixes:

 * switched to shared

See merge request nexedi/slapos!779

fixup of 6fbc6e15

The version we were using did not support timing diagrams.

Update to a more recent version where it's supported.

See merge request nexedi/slapos!778

This is a new feature requiring a recent plantuml version

Rendering of some diagrams to png is slightly different, images are not
same size

To fix caucased failures:
  File "caucase/caucase/http.py", line 799, in main
    http_cas=http_cas,
  File "caucase/caucase/http.py", line 397, in getSSLContext
    http_cas.createCertificate(csr_id)
  File "caucase/caucase/ca.py", line 281, in createCertificate
    template_csr=template_csr,
  File "caucase/caucase/ca.py", line 328, in _createCertificate
    x509.SubjectKeyIdentifier,
  File "cryptography-2.3.1-py2.7-linux-x86_64.egg/cryptography/x509/extensions.py", line 189, in from_issuer_subject_key_identifier
    key_identifier=ski.value.digest,
AttributeError: 'SubjectKeyIdentifier' object has no attribute 'value'

In turn, this requires updating cryptography dependencies.
In turn, this requires updating requests as our old version is
incompatible with current idna version.
In turn, this requires updating requests dependencies.
And finally, this allows/requires updating some pins in SRs:
- software/jupyter: Version up certifi.
- stack/erp5: Un-pin chardet, as it is already pinned at stack/slapos level.

Building PyPy from source is a nightmare and the shipped top-level
Makefile is a joke:
- nothing configurable at top-level to do the 2 common operations:
  build & install;
- the main binary searches for the library at hardcoded and
  undocumented places relative to where it is installed;
- no option to exclude specific components ? (here, _tkinter);
- lack documentation to specify location of required libraries;
- nothing out-of-the-box to build with several cores (it's even
  strange that in 2020, the biggest part is single threaded and
  it can't be resumed; I'm curious to know how developers work).

I found many answers in the Debian packaging.

This commit creates a Makefile file for 2 reasons:
- slapos.recipe.cmmi (forked from hexagonit.recipe.cmmi)
  does not have options to specify a shell snippet that is
  executed only during the build step
- by splitting the build in several steps, it makes debugging
  easier when it does not have to rebuild from the beginning

The drawback is that:
- make recipes need to be indented with tabs,
  in addition to the buildout indent of 2 spaces;
- $ escaping is tricky.

forcediphttpsadapter does not work with requests' SourceAddressAdapter,
so by following https://stackoverflow.com/a/44378047/9256748 implement
own curl's --resolve style.