For technical reasons the ? for Software Release allows simple hacky multiple
software releases to be created, which share exactly the same profile code,
and so JSON Schemas. So for such, use original Software Release JSON Schemas.

By default standalone will use the `slapos` executable in PATH.
This option allows a specific slapos binary to be used instead.

  For now we keep the same behaviour, before we upgrade into proper European/Chinese taxation models

   This change was requested by the accountant

slapos_erp5: Update security on tickets from the Project related to the computer or Hosting Subscription

   Filter Computer, Hosting Subscription and Computer Network to not display closed/destroy/invalidated ones.

This is to take advantage of !290

     Fix up when you pass path and when you pass the object for the newContent

    This allows user to get updated with the issued invoices.

   If Sale Invoice Transaction is already Grouped (Lettered), Cancel the related payment.

   This avoids edit already modified instances.

See merge request nexedi/slapos.core!293

Handle only public computers or forever closed, as other scopes are
reserved for personal or project usage.

Add the minimum hateoas support required for the cli commands:
- `slapos service list`
- `slapos service info <reference>`
- `slapos computer list`
- `slapos computer info <reference>`

To enable hateoas, complete the slapos.cfg configuration with:
```
[slapos]
master_rest_url = <proxyaddr>/hateoas
```

Also: Fix some bugs and python3 incompatibilities in slap/hateoas.py.

See merge request nexedi/slapos.core!290

libanl is part of glibc since 2001 (see
https://sourceware.org/git/?p=glibc.git;a=blob;f=ChangeLog.old/ChangeLog.12;h=adcf9081d44c06e03c3899612afba7c8c0d9b3fa;hb=HEAD#l5595)

See merge request nexedi/slapos.core!291

   This script isn't used, and every custom project might overwrite it, so no need to keep it.

   This makes management easier.