To isolate log files per test in the snapshots

Log files from slapos node software are large and they are always the
same after each test method, so it does not make much sense to store
them for each test method snapshot, because we only run slapos node
software at setupModule step.

Log files from slapos node instance are smaller, but it's also not
needed to make a snapshot after each test, because we only run slapos
node instance at setUpClass step.

To prevent duplication, store slapos log files only at setupModule (for
software) and at setUpClass (for instance).

Also store log slapos log files in all the steps that can fail in
_cleanup.

Everything in etc can be interesting while investigating issues in
test, also it should not be too big.

It's also interesting to see what scripts have been generated

Keeping buildout.cfg and .installed.cfg can help diagnosing test
failures.

Directories were ignored by mistake, we found out that several files
that would help us diagnosing problems were missing, because we only
snapshot etc/* which did not snapshot recursive directories such as
etc/promise or etc/service.

Symlinks were copied (the target was copied), because they matched the
isfile check, but if the symlink target was not existent, this caused
errors.

Also rename _snapshot_instance_file to _copySnapshot as it is no longer
treating files only

50 was too much now that we keep snapshots in tests.

supervisor configuration is interesting to inspect in, the same for runners
in run and service directories.

/reviewed-on nexedi/slapos.core!170

And display a "logout" button in the page.
Instead display plain renderjs error message

Probably this alarm should move into some other bt5 in future.

Add a mock for absolute_url as the test requires a valid url

The supervisord binary in some environments (like webrunner), seems to not
follow the automatic way to find the configuration file, so instead of relying
on it, just explicitly provide the file.

/reviewed-on nexedi/slapos.core!168

Add a mock for absolute_url as the test requires a valid url

 Those values shouldn't be applied on production

slapos_payzen; Scripts moved to slapos_account in order to make it compatible with multiple payment types

slapos_accouting: Scripts moved from slapos_payzen to make it compatible with multiple payment types

For now Payzen and Wechat

Depending on the netifaces version the netmask can come with or without
lenght prefix, so support both cases and consider netmask with prefix
as equal to without prefix.

The only result will be update of the netmask in the computer XML file.

self.interface.getGlobalScopeAddressList which uses netifaces can have
different sorting of the addresses depending of the version, so prefer the
already configured IPv6 address.

According to this [code](https://lab.nexedi.com/nexedi/slapos.core/blob/master/master/bt5/slapos_jio/PathTemplateItem/web_page_module/rjs_gadget_erp5_page_slap_computer_view_js.js#L127) . I believe the test `testSlapOSJSServer` currently failed due to a typo. There may have other failing in this test, but at least we can fix this one first.

/reviewed-on nexedi/slapos.core!165

This isn't the most suitable script for this anymore or some extra configurations can be used.

mostly copied from slapos_payzen