Tickets should be automatic suspended if they aren't supposed to be responded by the user.

This API is used by anonymous so we convert the query for the rely on shadow person security

Promise can appear and disappear, and pyc or pyo files can stay in the folder,
so try hard to remove those stale files.

/reviewed-on nexedi/slapos.core!169

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

/reviewed-on !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 !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

In Gitlab,  if URL is like https://USERNAME:PASSWORD@somedomain.com then gitlab will return 401 and ask for basic Authentication.

For this kind of URL, we simply extract username and password and send ajax request with Basic Auth.

/reviewed-on !163