file /usr/lib/systemd/system/bootc-generic-growpart.service is not owned by any package

I use quay.io/fedora/fedora-bootc:41 as a basis for my images, part of which includes removing packages that are not needed.

I've noticed that the bootc-generic-growpart.service starts to show up as failing once I boot the smaller image:

× bootc-generic-growpart.service - Bootc Fallback Root Filesystem Grow
     Loaded: loaded (/usr/lib/systemd/system/bootc-generic-growpart.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf, 50-keep-warm.conf
     Active: failed (Result: exit-code) since Wed 2024-12-18 04:02:54 EST; 1h 26min ago
   Duration: 26ms
 Invocation: 134d9e33f8774b6795c5b0cb51269072
       Docs: https://gitlab.com/fedora/bootc/docs
    Process: 961 ExecStart=/usr/libexec/bootc-generic-growpart (code=exited, status=1/FAILURE)
   Main PID: 961 (code=exited, status=1/FAILURE)
   Mem peak: 3.2M
        CPU: 14ms

Dec 18 04:02:54 fedora systemd[1]: Started bootc-generic-growpart.service - Bootc Fallback Root Filesystem Grow.
Dec 18 04:02:54 fedora bootc-generic-growpart[961]: Backing device: /dev/vda3
Dec 18 04:02:54 fedora bootc-generic-growpart[970]: /usr/libexec/bootc-generic-growpart: line 31: /usr/bin/growpart: No such file or directory
Dec 18 04:02:54 fedora bootc-generic-growpart[961]: growpart failed
Dec 18 04:02:54 fedora systemd[1]: bootc-generic-growpart.service: Main process exited, code=exited, status=1/FAILURE
Dec 18 04:02:54 fedora systemd[1]: bootc-generic-growpart.service: Failed with result 'exit-code'.

I first thought that the package which brings that .service does not properly rpm-require the package which ships /usr/bin/growpart (cloud-utils-growpart-0.33-9.fc41.noarch) ... but to my surprise, rpm -qf /usr/lib/systemd/system/bootc-generic-growpart.service shows that the .service got to the image via some nonstandard rpm mechanism.

Would it be possible to just package it as an rpm?