same as nexedi/erp5@2e366054

With the previous approach, the test depend on the order of attributes,
but this order is not stable when hash randomization is enabled and we
don't care about order of attributes in this test.

This is no stable with hash randomization, with PYTHONHASHSEED=593 this
test failed.

slapos_cloud:testSlapOSCloud fails with PYTHONHASHSEED=385

this is done by upgrader in production, so it's consistent to do it
before test

sorted and with the usual workaround for trailing space bug

See merge request nexedi/slapos.core!613

See merge request nexedi/slapos.core!614

  This is quite specific to project based instances, so no need to add into every instance

  Test some particular cases or features that MUST not be used, to ensure nobody the editor is handling it properly.

See merge request nexedi/slapos.core!609

See merge request nexedi/slapos.core!612

  Latest version had significant changes, so pin the version for now

See merge request nexedi/slapos.core!611

Since ERP5 commit 6546e47f51 (erp5_software_pdm: a Software Product is
a Service, 2022-09-07), the message changed

  This cause editor do not render the form.

   It is better use the parameter_xml directly since, since there are no need for the editor
   handle hashed version of the parameters.

It's been a while the server is ready.

See nexedi/erp5@c45c2295

   Replace it with an generic action directly pushed to erp5 (erp5_forge)

See merge request nexedi/slapos.core!606

   This prevent raise in case some non-ascii char is passed into the string.

  We only expand by the end of the period, so we dont generate an invoice 15 days in advance anymore

- make url script return no url if there are not connection parameters
- update tests accordingly

   ...to failures on password generation

See merge request nexedi/slapos.core!604

See merge request nexedi/slapos.core!603

   The password has to work accordinally the policy, if fail retry a few times.