Refactor some default value handling in transforms
Refactor some default value handling in transforms

  - Make sure every transformed MaxNumOfVmCpus has a DEFAULT_ARCH value

    Transforming `EngineOptionMaxNumOfVmCpusPerArch` will now make
    sure that every `MaxNumOfVmCpusPerArch` will contain a `DEFAULT_ARCH`
    value equal to 1.  That way, if a cpu architecture for an entity is
    not available, or if an architecture is removed, changed, added
    or deleted, the default will be there and the app will not fail.

  - Update transform toInternal `cpuOptions` default values to -1

    Since the fetch sagas will reset the `cpuOptions` as appropriate
    when the entity is loaded, the initial values in the transform don't
    matter.  To make it easier to spot if the fetch sagas fail, the initial
    values are all set to -1.  Seeing a -1 in any `cpuOptions` entry of
    any given entity indicates the fetch saga is broken.

oVirt/ovirt-web-ui,oVirt/ovirt-web-ui,oVirt/ovirt-web-ui