Upgrade system: new db migration mechanism, add images types

* Implemented new database migartion mechanism, we don't use
  shared volume, we use pg_dumpall to take database from
  previous container, and then we add it in new container.
  We assume that db migration applied by puppet when
  supervisor starts container. As result we removed a lot
  of hardcoded logic.
* Added images types, it's important because we have containers
  like busybox which don't have fuel prefixes and postfixes.
  In images section of config was added new field `type`
  which can be `base` or `fuel`. Also we don't need delete
  `base` when upload new images.
* Upgrade checker. It's very important part of the system
  which can tell us if upgrade succeed, now we have simple
  checks for each service. If verification failed, we run
  rollback system.
* Fixed volume_logs container bindings.

blueprint upgrade-to-5-1
Change-Id: I3667e74c24472626de81603929a1fc24074c1e71
Merge "Upgrade system: new db migration mechanism, add images types"