core: InternalMigrateVmCommand cleanup

Replaced convertInternalMigrateParamsToMigrateParams method in
InternalMigrateVmCommand with a constructor in MigrateVmParameters that
gets as an input InternalMigrateVmParameters instance.

InternalMigrateVmParameters class was moved to
org.ovirt.engine.core.common.action package so that it will be
accessible from MigrateVmParameters class (and that package it should be
in anyway as all the parameters class resides there)

On the way two minor changes were made in order to support later
patches:
1. a constructor that also gets the parent command was added to
InternalMigrateVmParameters
2. the correlation-id is also copied from the
InternalMigrateVmParameters on the newly added constructor in
MigrateVmParameters

Change-Id: Idfeb4966b6ae0a570904861a5e6b1768b0c6d47f
Signed-off-by: Arik Hadas <ahadas@redhat.com>
core: revert change If615a9d9

In patch If615a9d9 the execution context of SetNonOperationalVdsCommand
changed to async if it triggered migrations.

This patch change its execution context back to sync. migrations that
will be triggered from SetNonOperationalCommand will be executed as
different jobs (it will be pushed in a different patch), thus resolving
bug 888199 without making the set-non-operational command to be async
(this command shouldn't be async, as the host become non-operational
right after the sync part, independently from the triggered migrations)

Change-Id: I91eb9e84d0ff4ce6a0c8390dc973c3f8822a0c8c
Signed-off-by: Arik Hadas <ahadas@redhat.com>