Fixed IBM-Cloud-Standard profile

The test-image-MicroOS integration test builds an IBM-Cloud-Standard
profile as encrypted variant with a random key that is not protected
by an encrypted boot image. This doesn't make sense. Thus the
encryption setup for the IBM cloud standard build got removed.
Use the IBM-Cloud-Secure-Execution profile to test encrypted
secure linux builds

Author: schaefi

build-tests/s390/tumbleweed/test-image-MicroOS/appliance.kiwi

@@ -21,24 +21,16 @@
     <preferences profiles="IBM-Cloud-Standard">
         <type
             image="oem"
-            luks="random"
-            luks_pbkdf="pbkdf2"
-            luks_version="luks2"
             filesystem="btrfs"
             kernelcmdline="systemd.show_status=yes console=ttyS0,115200 console=tty0 net.ifnames=0 \$ignition_firstboot ignition.platform.id=qemu rd.debug"
             devicepersistency="by-uuid"
             btrfs_root_is_snapshot="true"
             btrfs_root_is_readonly_snapshot="false"
             btrfs_root_is_subvolume="true"
             btrfs_quota_groups="true"
-            bootpartition="true"
-            bootfilesystem="ext3"
+            bootpartition="false"
             format="qcow2"
         >
-            <luksformat>
-                <option name="--cipher" value="aes-xts-plain64"/>
-                <option name="--key-size" value="256"/>
-            </luksformat>
             <oemconfig>
                 <oem-unattended>true</oem-unattended>
                 <oem-resize>true</oem-resize>