Use the same /etc/resolve.conf in kdump initrd if it's managed manually
    
    Resolves: https://issues.redhat.com/browse/RHEL-11897
    Upstream: Fedora
    Conflict: None
    
    commit 38d9990389d80039964668a4db9cc9c039eac68f
    Author: Coiby Xu <coxu@redhat.com>
    Date:   Tue Dec 26 11:17:29 2023 +0800
    
        Use the same /etc/resolve.conf in kdump initrd if it's managed manually
    
        Resolves: https://issues.redhat.com/browse/RHEL-11897
    
        Previously fix 0177e248 ("Use the same /etc/resolve.conf in kdump initrd
        if it's managed manually") is problematic,
           1) it generated .conf file unrecognized by NetowrkManager ;
           2) this .conf file was installed to current file system instead of to the kdump initrd;
           3) this incorrect .conf file prevented the starting of NetworkManager.
    
        This patch fixes the above issues and also suppresses a harmless warning
        when systemd-resolved.service doesn't exist,
    
            # systemctl -q is-enabled systemd-resolved
            Failed to get unit file state for systemd-resolved.service: No such file or directory
    
        Fixes: 0177e248 ("Use the same /etc/resolve.conf in kdump initrd if it's managed manually")
        Reported-by: Jie Li <jieli@redhat.com>
        Cc: Dave Young <dyoung@redhat.com>
        Reviewed-by: Dave Young <dyoung@redhat.com>
        Signed-off-by: Coiby Xu <coxu@redhat.com>
    
    Signed-off-by: Coiby Xu <coxu@redhat.com>