kdumpctl: Only returns immediately after an error occurs in check_*_modified
    
    Resolves: https://issues.redhat.com/browse/RHEL-10484
    Upstream: Fedora
    Conflict: Missing upstream patch d4e8772("kdumpctl: make do_estimate more
    robust")
    
    commit 741861164e24247e995d47a8284b7493cb73b769
    Author: Lichen Liu <lichliu@redhat.com>
    Date:   Mon Oct 30 14:51:59 2023 +0800
    
        kdumpctl: Only returns immediately after an error occurs in check_*_modified
    
        Currently is_system_modified will return immediately when check_*_modified
        return a non-zero value, and the remaining checks will not be executed.
    
        For example, if there is a fs-related error exists, and someone changes the
        kdump.conf, check_files_modified will return 1 and is_system_modified will
        return 1 immediately. This will cause kdumpctl to skip check_fs/drivers_modified,
        kdump.service will rebuild the initrd and start successfully, however, any
        errors should prevent kdump.service from starting.
    
        This patch will cause check_*_modifed to continue running until an error occurs
        or all execution ends.
    
        Signed-off-by: Lichen Liu <lichliu@redhat.com>
        Acked-by: Tao Liu <ltao@redhat.com>
    
    Signed-off-by: Lichen Liu <lichliu@redhat.com>