Unify Runtime Systemd Service Files for both ISO/KIC

[medyagh]

while bumping crio here #22332 I noticed
we have our own service file for crio in ISO that we pass minikube options to it
for example

ExecStart=/usr/bin/crio \
          $CRIO_OPTIONS \
          $CRIO_MINIKUBE_OPTIONS

however in KIC we just install it from upstream and have vanila crio config.

the good thing about upstream is we get fresh new service files(they dont change as often but they do)
but bad thing about using upstream is we dont pass miinikube options such as --insecure-registry to it
and might be reason why CRIO in kic has way more failures in tests.

it would be nice to have this unified when we move to https://github.com/kubernetes-sigs/minikube-os

[balnc9]

hello i'd like to work on this issue
if i understand correctly, a possible solution could be to add a custom crio.service @ deploy/kicbase/crio.service (similar to what iso uses) that reads the sysconfig environment files, and update the Dockerfile to copy it and create /etc/sysconfig/crio just with default options.
happy to submit a PR if this approach checks out!