NamedTemporaryFile are w+b by default.

In deploy test, this recipe is used with url encoded POST [1], but the
test only tested multipart encoded POSTs. In python 3, they are different,
with multipart POSTs, FieldStorage values are bytes, but with url encoded
POSTs, the values are string.

This small server from the recipe only supported multipart POSTs, this
change add support for url encoded POSTs.

[1]: https://lab.nexedi.com/nexedi/slapos/blob/dd7038feab70866e54028de89d0e0e1017fc276c/software/erp5testnode/testsuite/deploy-test/deploy-script-controller#L86

Result of getSoftwareURL can contain other replacements, so replace it very
early in order to avoid such issue.

This test is always failing and it's impossible to fix it (for now). As this
is well known issue with some workarounds available mark it with
expectedFailure.

Add a new SR to deploy scripts on drones to fly them

Add QuickJS wrapper for MAVSDK and open62541 librairies

Add the collection of libraries to interface with MAVLink systems mavsdk

This is the case in debian 11 when we don't have python2 installed.

See merge request nexedi/slapos!1247

this package is python3

We no longer need backports.lzma now this test is python3 only

Now that all the problems of running a different version of python in
slapos-node and within the software and now that slapos-node always run
on python3, we no longer need to have two separate test softwares and
two separate suites for python2 and python3 - we have one test suite
for all our softwares, regardless of the python version used by these
softwares and this test suite use python3 to run the tests code and to
run slapos-node

On modern systems it is not installed and anyway slapos should not
depend on host system programs.
Basically same fix as b964b95b (software/fluentd: Fix SR test on Debian
11, 2022-01-04)

we'll only run the test on python3

See merge request nexedi/slapos!1228

mca--static.cfg provides a statically linked version of mca.
"dep--" means it does not compile all the building dependencies.

Sometimes backends process less than 15% of requests. For this test to
test that the requests are distributed on all backends, testing that
each backend process at least one request should be enough.