We only had a global "pidfile" configuration, but it's more conveniant
to be able to configure different pidfile for each command (software,
instance, report)

The supported config file would look like:

```
[slapos]
pidfile_software = /path/to/pid
pidfile_instance = /path/to/pid
pidfile_report = /path/to/pid

```



/reviewed-on !29

  Include a test for fetch configuration

  Conflicts on namespace can easily break this feature, so pick the
  template directly is safer.

  The skins should be automatically indexed while install the bt5s.

  The new implementation with hateoas API is under development so there is no need
  to expent time on fix those tests now.

This pluging can be used a add a script which wipe data before the partition is removed
The script run after all partition services are stopped. The script is ran by supervisord
then slapos node report will wait until it finish before destroy the partition.

/reviewed-on nexedi/slapos.core!23

This pluging can be used a add a script which wipe data before the partition is removed
The script run after all partition services are stopped. The script is ran by supervisord
then slapos node report will wait until it finish before destroy the partition.

/reviewed-on nexedi/slapos.core!22

No need 2 bt5 with similar goal.

This code is old code for JIO which were never used in the end, clean up for the next implementation.

  This change were commited by mistake

  Get the person created by searching the ERP5 Login, because person has not reference defined.

- Use getUserId instead getReference for person login on self.login method
- Get the person created by searching the ERP5 Login, because person has not reference defined.

slapos_erp5: testSlapOSERP5LocalPermissionSlapOSInteractionWorkflow use person.getUserId instead person.getReference

Follow up changes on erp5 security.

Follow up implementation of ERP5LoginUserManager.

Follow up changes from ERP5Security.

This API was changed, so follow up changes which come from ERP5.

  Remove useless imports
  Use ERP5Security.SUPER_SUPER instead SUPER_USER to follow up original code.
  Also use UnrestrictedMethod on SlapOSShadowAuthenticationPlugin

  Reference commit erp5@455b24e5

 This change follow changes on ERP5 code base:
  nexedi/erp5@4b16e1dd

  By invoking validate, the interaction workflow will be kicked and allocation will be triggered. In order to control the invocation order on the test, use portal_workflow API.

  This test is failing as it is incompatible with the latest version of renderjs. The Monitor UI is going to be merged into RenderJS, so keep this test as an expected failure until this test be moved along with monitor implementation to ERP5/OfficeJS repository.

Person.getTitle do not contains patches for a while so we fall back on default the implementation of ERP5. This don't require mantains a test on project scope.