- Remove the top-level Makefile of the archive.
- Rename directories.
- Send directly tarballs/$SOFTWARE.
- Build from tarballs/$SOFTWARE/Makefile.
- Rename variables for clarity.
- Add obs.sh and clean_obs.sh.

- remove template/networkcached.cfg.in
- remove the networkcached support from build_tree.sh and clean_build_tree.sh
- remove the networkcached support from template_stage.sh bootstrap_buildout.sh
- remove cache_creation.sh and clean_cache_creation.sh

The scripts do everything until the first run of buildout (actual run, not just bootstraping).

Previously it only worked with Debian 10. This commit reflects the
removal of the apt package 'python-pip' in Debian 11 and the change
of the i2c bus number.

There were still two issues which are solved with this commit:

1. Previously the firewall prevented the installation of Fluentd
   (because no connection via http/https was possible).

2. Previously the sensor couldn't send data to the IoT gateway (
   the opened port wasn't sufficient).

When importing the slapos playbook after running re6stnet-install role,
the user defined computer_name will be ignored and will be overridden
by 'set_facts', line 16 in re6stnet-install/tasks/main.yml. Therefore
the slapos install role is directly called (instead of importing the
playbook) which seems to solve the issue.

(due to activated firewall)

(wrong indentation)

(wasn't possible because of too restrictive ipv6 firewall)

Add restrictive firewall settings to avoid any security risk.

Bug appeared due to wrong pip version. Therefore the version has been
set explicitly.

Now the Python script name is consistent with the file name in the
Fluentd config file as described in the learning track.

Should be installed via rapid.space panel.

Previously it failed because setuptools wasn't installed.

Replaced 'computer_name' with 'computer_id'. Previously I confused both.
Now the user has to enter the respective computer reference.

It won't run in an issue anymore if the file already exists.

Fluentd couldn't be installed because we first have to configure the
SlapOS client via `slapos configure client` before being able to use
`slapos console` (to supply and request Fluentd from a Python script).

In the Wendelin learning track this permission is granted to the user via
"chgrp SLAPUSER /dev/i2c-3". Because we don't know the particular
slapuser we have to add the permission to all users of the slapsoft
group. Because /sys/bus/i2c/devices/i2c-3 is a virtual directory and
we want to make sure that even after rebooting or unplugging /
replugging of the sensor the permission is still granted udev rules
have been added.

Initial commit for adding automatic preperation of Olimex boards as an IoT Gateway
and for a Sensor to send data to Wendelin (see
https://wendelin.nexedi.com/wendelin-Learning.Track/wendelin-Tutorial.Setup.Sensor.IOTGateway/WebPage_viewAsWeb
).

Since tests are launched inside namespace, we don't have SUID ping
available anymore so we explicitely allow all users to do ping.

Please note that this works for both IPv4 and IPv6 despite the name.

See slapos!1107 (comment 148968)
for more information.