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 0177e24832e8d3e5ea2e033c55b616bdd0cf3e9b
    Author: Coiby Xu <coxu@redhat.com>
    Date:   Tue Nov 7 08:28:59 2023 +0800
    
        Use the same /etc/resolve.conf in kdump initrd if it's managed manually
    
        Resolves: https://issues.redhat.com/browse/RHEL-11897
    
        Some users may choose to manage /etc/resolve.conf manually [1]
        by setting dns=none or use a symbolic link resolve.conf [2].
        In this case, network dumping will not work because DNS resolution
        fails. Use the same /etc/resolve.conf in kdump initrd to fix this
        problem.
    
        [1] https://bugzilla.gnome.org/show_bug.cgi?id=690404
        [2] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/manually-configuring-the-etc-resolv-conf-file_configuring-and-managing-networking
    
        Fixes: 63c3805c ("Set up kdump network by directly copying NM connection profile to initrd")
        Reported-by: Curtis Taylor <cutaylor@redhat.com>
        Cc: Jie Li <jieli@redhat.com>
        Signed-off-by: Coiby Xu <coxu@redhat.com>
        Reviewed-by: Dave Young <dyoung@redhat.com>
    
    Signed-off-by: Coiby Xu <coxu@redhat.com>