use /run/ostree-booted to tell if scriptlet is running on OSTree system
    
    Related: bz2048690
    Upstream: Fedora
    Conflict: None
    
    commit f6bcd819fc2645f762946a802c15684e7627f379
    Author: Coiby Xu <coxu@redhat.com>
    Date:   Fri Jul 15 15:11:44 2022 +0800
    
        use /run/ostree-booted to tell if scriptlet is running on OSTree system
    
        Resolves: bz2092012
    
        According to the ostree team [1], the existence of /run/ostree-booted
        > is the most stable way to signal/check that a system has been
        > booted in ostree-style.  It is also used by rpm-ostree at
        > compose/install time in the sandboxed environment where scriptlets run,
        > in order to signal that the package is being installed/composed into
        > an ostree commit (i.e. not directly on a live system).  See
        > https://github.com/coreos/rpm-ostree/blob/8ddf5f40d9cbbd9d3668cc75b703316e0a89ab11/src/libpriv/rpmostree-scripts.cxx#L350-L353
        > for reference.
    
        By checking the existence of /run/ostree-booted, we could skip trying to
        update kernel cmdline during OSTree compose time.
    
        [1] https://bugzilla.redhat.com/show_bug.cgi?id=2092012#c3
    
        Reported-by: Luca BRUNO <lucab@redhat.com>
        Suggested-by: Luca BRUNO <lucab@redhat.com>
        Fixes: 0adb0f4 ("try to reset kernel crashkernel when kexec-tools updates the default crashkernel value")
        Signed-off-by: Coiby Xu <coxu@redhat.com>
        Reviewed-by: Philipp Rudo <prudo@redhat.com>
        Acked-by: Timothée Ravier <siosm@fedoraproject.org>
    
    Signed-off-by: Coiby Xu <coxu@redhat.com>