Use dev registry for cilium artifacts in dev bundle

As mentioned in #1629, we are not using our dev repo path for cilium artifacts on the registry. We also seem to have different naming for other images, such as `/l0g8r8j6/kubernetes-sigs/cluster-api/kubeadm-bootstrap-controller`, so maybe we can use `l0g8r8j6` as the common repository instead to make it consistent with our other images.

Start by tracing how the dev bundle defines registry paths for Cilium artifacts, then compare them with the example cluster-api image naming in the issue and the context from #1629. Done means the dev bundle uses the intended dev repository path and its artifact naming is consistent with the other images.

Written by the indexing model from the issue text.