slapos_cloud/SlapOSTestCaseDefaultScenarioMixin: Subscription allocation scope behaves like Public ones

This intend to reproduce the behaviour when monitor/upgrade based on allocation scope only.

Changes are related to the usage of monitor_scope definition.

This eliminates need of extra configuration or check yet another page for most of the users.

computer_install_command_line allows you configure the installation command for a computer (per website)

slapos_master_api allows you define where computers may connect to this master specifically.

This reverts commit 18ee7dad

/reviewed-on !107

configure local: Generate slapproxy conf for supervisord first, then supervisord certainly start slapproxy. Before this commit, slapproxy often did not start after "slapos configure local", that was because slapproxy conf did not exist when supervisord was launched.

See e02b451e for original commit

On some systems netmask can already contain /<bits>, so just use the
nu.me.ri.cal value.

/reviewed-on nexedi/slapos.core!106

Update the API to remove the additional get to get monitoring status information, this may cause a major improvement in speed, as the most of the queries to master are removed.

The initial "news" information is passed as parameter

  Indicate when instance is Slave, Stopped or Destroyed on the News Dict
  Display monitor url and more information on the monitor gadget

This API is deprecated, replaced by appropriated one

slapos_jio: Send connection parameters as part of the API for Hosting Subscriptions and Software Instances

The information can come to listbox or come as RAW to the query, allowing us to hight light some informations.

Since the compatibility with PY3.

This makes dev instance and production the similar.

Keep consistency with others alarms enabled related to upgrade.