core: jobs/steps/audit log handling for domain deactivation

When a Storage Domain is being deactivated, we first attempt to update
the OVF data on the domain and only afterward attempt to deactivate it.
The OVF update phase may contain create volume operations (in case more
OVF stores are needed) and upload image operations afterwards (to update
OVF data contained on the OVF stores).

This patch handle the jobs/steps of the deactivation scenario, so that
on the EXECUTING step all the Upload/Create Image tasks will appear.

Furthermore, when the execution is initiated by the user there's no
need to log that there are tasks, as the tasks were created by the
flow itself (it's being checked on the CDA phase that there are no
tasks prior to the execution).

Change-Id: I4cde77da50fe63a4fda6d9fb61e95fc113e4b54c
Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1138124
Signed-off-by: Liron Aravot <laravot@redhat.com>
core: correct ProcessOvfUpdateForStorageDomainCommand lock properties

ProcessOvfUpdateForStorageDomainCommand lock is released always on the
execute phase prior to change I54cc929937d3b14dc49a2edab9e763cbe603a9c3
- either by the child command or because the created tasks aren't added
to the command task
list.

This patch changes the applyLockProperties method to state that
explictly.

Change-Id: I938e8a0ce74bb931635948210f26a1f451fbe815
Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1138124
Signed-off-by: Liron Aravot <laravot@redhat.com>