- fixed initrd creation for ec2 images done with mkinitrd
  * For EC2 images kiwi uses mkinitrd to create a targeted for EC2 initrd,
    rather than the usual kiwi initial intrd that generates a new initrd
    on firstboot. With SLE 11 SP3 mkinitrd got "smarter" to the
    disadvantage of building an initrd on system A that is targeted for
    system B. Therefore we were forced to create a so called "monster
    initrd". This monster initrd include basically everything, hence the
    name. While this in general is only a minor size concern in EC2 this
    has the ill effect that the image will not boot. The reason for the
    non booting image is the inclusion of multipath in the initrd.
    This patch moves the 61-multipath.sh away for the call of mkinitrd
    and put it back afterwards
- cleanup getBootIncludePackages(), I thought comments and
  variable names are misleading
- fixed handling of bootincluded items:
  * packages and archives marked as bootinclude have to
    respect an optional arch setup like this example:
    <package name="foo" bootinclude="true" arch="ix86"/>
- make sure setupBootLoaderGrub2() creates /boot/grub2/device.map
  which is required for suse tools to work correctly