It is required due the replacement of the ownership.

   Sometimes the instances where the data is commited, don't have the same user set as the tests.

   Remove useless duplication on the security test (just duplication)
   Remove and include test for Organisation

  Move access into assignment based security

   Open tickets have to be handled by Administrators, and not by the user, only suspended tickets or confirmed upgrade decisions should be displayed on the front page, as it is duty of the user respond them.

slapos_subscription_request: (Test) Verbose why the subscription request isn't ordered by the script.

With nexedi/slapos!862 we no longer need this

See merge request nexedi/slapos.core!270

   Only assert the essential, otherwise any minor change on the zpt is a useless diff that pops up

  Mock NotificationTool_getDocumentValue to ensure the None as return value, in order to not find eventual valid notification messages with random content from other tests or dev environment.

  No need to assert entire message, it is enought to assert message isn't empty and assert a subset of it.

   This allows extend values w/o duplicate the whole test.

   Simplify the extensions on testSlapOSConfigurator to the expected bt5 and modules list

   This allow us to translate and re-run the tests with real notification messages.

   It ensure that selected payment is from the proper user.

  Also, keep paths specific to not conflict with extra business templates. We don't
  want a polluted list after the installation of extra bt5 on development or
  project specific environments.

   This allow introduce minor custom changes on project specific context w/o re-implement the whole test.

   This makes easy to overwrite and custom the list on sub-level projects

we no longer use python setup.py test

We were doing this because we use to run tests with `python setup.py test`
which automatically sets PYTHONPATH, so it was affecting sub processes
started by standalone.

Nowadays we no longer use this method of running tests, so we are not really
supposed to use PYTHONPATH, so we don't unset this environment variable,
there might be valid cases where users want to force a different python path
(but I can not think of any) and it simplifies the code a bit.

    Reported-by: Romain