rules: implement new memory hotplug policy
    
    Our new policy is based on following motivations (assumptions),
      * we want to allow the system to use hotplugged memory
      * we want memory ballon inflation to work as expected in VMs (going for small
      to big in terms of memory footprint)
      * we want to allow memory hotplug and memory hot-unplug on high-end
      enterprise server (we assume that node0 will have sufficient memory
      resources and marking all memory as movable shouldn't be a problem)
    
    Policy:
      * nevert online memory on s390 (on both physical and z/VM)
      * mark memory as "online_movable" on physical machines
      * mark memory as "online" in VMs
    
    If you have the feeling that all this is very wrong and we shouldn't
    encode complex policies in udev rules you are absolutely right. However,
    for now, we don't have any better place where to put it. In ideal world
    we would have a user-space daemon that would be able to configure the
    system wrt. to currently present HW and user-defined policy.
    
    Resolves: #1670728
    
    patch_name: 0091-rules-implement-new-memory-hotplug-policy.patch
    present_in_specfile: true
    location_in_specfile: 91
    squash_commits: true