The `lsb_release` command is required in order to run the playbook,
because it uses `ansible_lsb`.
Otherwise, the following error is raised:

```
fatal: [127.0.0.1]: FAILED! => {"msg": "The conditional check '(ansible_distribution == \"Ubuntu\" and ansible_distribution_version == \"20.04\") or (ansible_lsb.codename == \"kylin\" and ansible_lsb.major_release == \"v10\")' failed. The error was: error while evaluating conditional ((ansible_distribution == \"Ubuntu\" and ansible_distribution_version == \"20.04\") or (ansible_lsb.codename == \"kylin\" and ansible_lsb.major_release == \"v10\")): 'dict object' has no attribute 'codename'. 'dict object' has no attribute 'codename'\n\nThe error appears to be in '/tmp/tmpplaybook_unstableslapos.27149/roles/repository/tasks/main.yml': line 91, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n  - name: Install Ubuntu 20.04 repository key\n    ^ here\n"}
```

As the package containing `lsb_release` is different on different Linux
distros, this commit only attempts to install it in SLE 16 SP6, where
it is called `lsb-release`.

  This was causing bt5 to generate delta while export.

  Merge the delta, minimizing the diff on the fork of the file.

  Currently, it is not used on general code. Since it is not used
  we are dropping from our codebase. Nothing prevents other projects
  include it in future.

See merge request nexedi/slapos.core!639

- do not return url if connection parameters are not available
- use byteify instead of encode to handle dict json data
- drop obsolete setting_configurator url
- drop json loads/dumps
- set slapos master url parameter

   Whenever an Instance Tree is destroyed (and archived), cancel the Subscription Request
   on Submitted state.

    This is required since the Submitted Subscription Requests count as required Deposit, and
    the user clearly didnt conclude his payment.

   Similar to "Pay" Section, it will display the outstanding amount right the way to pay. This allows the user "immediately" have their instance ready to allocate (validated) and it wont require to navigate to pay section or subscription request.

   This allows the script been used with normal user security roles,
   since only account_module is cause restrict access (by the current
   usage).

   destination section can be an organisation, so use shadow to avoid
   relax security.

   Display if the instance is payable (price currency/unit)
   Create and redirect to deposit payment if balance would require a deposit to the instance to work.

  This allows to to getPrice before actual create a subscription request.

* add 'Add Event' action on the panel
* display discussion on the upgrade decision

Allow to upload an attachment when creating an ticket's event.

The text_content parameter is limited to text/plain.
More work is required to support text/html content_type.

In Suse SLE 15.6, ansible can be installed either from the OpenSuse
repo of from PackageHub.

The version installed from OpenSuse requires Python >= 3.10.
Thus, it depends on the modern Python (version 3.11) provided by the
Python 3 module, instead of on the Python provided by the base system
module (version 3.6).
Packages installed for the modern Python, such as pip, will have
python311 as a prefix instead of just Python.

On the other hand, the ansible version in PackageHub is older and
can be used with the older Python version.

Thus, we check if either version of the package is installed, and if
not we install the more modern from those available.

See merge request nexedi/slapos.core!647.

also remove lab.node.vifib.com old URL. The URLs we support for gitlab
are:
 * lab.nexedi.com
 * lab.nxdcdn.com
 * lab.nexedi.cn

`SuSE-release` was deprecated and missing in new distributions in favor of `os-release`.

See merge request nexedi/slapos.core!628

Previous messages were all showing relative URL of the object on which the script was executed.
This was likely a typo in the script and made messages unreadable. This commit restores proper behaviour.

   Probably it comes from a bad copy and paste, since it contains mostly payzen references.

   Create the documents on the fly on the tests, otherwise it may cause problems on production.