Seeder gets stuck if cluster is deleted/re-created mid creation

[m-ildefons]

Seeder can get stuck if actions are taken on the Clusters.metal object in the K8s API while BMCJobs/BMCTasks are executed:

{"level":"error","ts":1724167090.4703617,"msg":"Reconciler error","controller":"inventory","controllerGroup":"metal.harvesterhci.io","controllerKind":"Inventory","inventory":{"name":"hp-199","namespace":"seeder"},"namespace":"seeder","name":"hp-199","reconcileID":"2a6179e8-0172-47f3-8d6b-513dea6cc28b","error":"bmcjobs.bmc.tinkerbell.org \"hp-199-reboot\" already exists","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:273\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:234"}

This leaves the cluster and the machine in limbo and needs to be recovered manually by removing the associated objects (cluster.metal, bmcjob, bmctask) and shutting down the machine before re-installing from scratch.