This is a fixup release, as 1.6.7 was missing important changelog.

See merge request nexedi/slapos.core!285

whitelistfirewall manager is locking down partition access as configured in
partition's .slapos-whitelist-firewall file by using firewalld configuration.

The md5sum of last generated partition whitelist file is used to take
decision if given rule shall be updated.

The manager supports partition setup and destruction.

Note: User id is used with netfilter owner module, as currently the sourcing
      address is not enforced to be per partition.

Despite promise failure, managers shall be executed, as often thanks to
running them, promise can be fulfilled.

    Whenever a rss feed is disabled, we can use this form to render a legacy message that changes url and pubDate once a day.

   A general warning can be issued to warn all users regardless the context. This is usefull for general mantainence or custom messages, while it is urgent inform users right the way.

Some recipes (like softwaretype) need a reference for the partition
address and in webrunner, we don't have tap interface.

/reviewed-on nexedi/slapos.core!287

Thanks to this it's possible to catch issues with firewalld

It's not used by us (controlled by supervisor), and would escape /opt/slapos
anyway.

   This introduce specific worklists

    This is a copy of validation_workflow however with specific audit worklists for SlapOS Master.

    If we use multiple titles, once cache is expired on memcached it creates multiples titles overtime.

   Include worklists for Regularisation requests

   This is part of automated process, so no reason for give write access on those events.

  Sale Packing List is fully automated on SlapOS Master, so Administrator shoudn't edit the packing lists.

   It requires args.

    This allows we calculate Outstanting Amout on subscription process (when user order from website)

   Fix up don't create line if line is found.

  This might help us locate insntances per its parameters.

   If the Slave Instance is root instance, we should allocated exclusivelly on Subscription defined computers/instances

  Adopt price based on Variations rather them on the lines.

   The goal is define pricing based on the Service Individual Variation in order to support multiple reservation fee prices.

   Introduce a CDN case with different reservation fee and monthly fee pricing.