This reverts commit 7f6729de.

ZODB has been switched to ZODB4 in 447b27e6 (Switch from ZODB3 (3.10.7)
to ZODB (4.4.4)) including raising transaction version requirement to
1.7.0 so we can try to introduce zodbtools one more time.

/proposed-for-review-on nexedi/slapos!121

Without it, the interest of tweaking the partition table is limited, because:
- it is impossible to free space efficiently
- 'optimize table' is even slower

slaprunner: export script shouldn't succeed if the backup of the contained instances are running at the same time

- version up: setuptools 30.1.0
- revert commit 1d0a8073

NEO is also not ready yet for transaction 2.x

This MR brings some confort of use and of administration for the resiliency stack and resiliency related taks :

   *  logrotate some logs/feeds to save disk space
   * adds more promises on export and import instances
   * improves feedback on import failures :  promises are more verbose, more information on the takeover webpage, ...
   * better indempotency for the backup time information, which is now published instead of read from the .installed.cfg

Updated on 11/22 : 

   * improve pbs recipe : makes the trap command cross-shell
   * remove infinite loops in scripts generated by pbs, but run a given amount of time until raising an error (which can be catched by promises)
   * runner-importer script doesn't systematically fails if there is no requested SR.
   * adds promises for notifier feeds (on exporter and pbs) to check last result and check if feed is corrupted

This MR should be merged after slapos.core has been upgraded 

/reviewed-on !115

/reviewed-on nexedi/slapos!117

resilient: adds a promise to test integrity and the status of the last run of the feeds generated by notifier scripts

Instead, of that, the notifier wrappers will run the scripts several more times in case of failures
This is better than silent failures.

  Introduce NGINX on the same partition of apache to handle websocket\
  and eventsource types.

  The NGINX will run on another port and it would require a second ip at
  the machine for enable it.

  This configuration is a working version with fully https support, but
  some additional adjustments might be required.