Offboarding via Hypervisor CRO

[fwiesel]

• Block gardener with pdb until offboarded
• Communicate offboarded via condition on hypervisor
• Do only decomissioning via hypervisor cro

Use offboarded instead of decomissioning as it
is clearer the opposite from onboarding.

[github-actions]

Merging this branch will decrease overall coverage

Impacted Packages	Coverage Δ	🤖
github.com/cobaltcore-dev/openstack-hypervisor-operator/api/v1	0.00% (ø)
github.com/cobaltcore-dev/openstack-hypervisor-operator/internal/controller	55.51% (-0.18%)	👎

---

Coverage by file

Changed files (no unit tests)

Changed File	Coverage Δ	Total	Covered	Missed	🤖
github.com/cobaltcore-dev/openstack-hypervisor-operator/api/v1/hypervisor_types.go	0.00% (ø)	0	0	0
github.com/cobaltcore-dev/openstack-hypervisor-operator/internal/controller/decomission_controller.go	54.69% (-3.75%)	64 (-13)	35 (-10)	29 (-3)	👎
github.com/cobaltcore-dev/openstack-hypervisor-operator/internal/controller/gardener_node_lifecycle_controller.go	64.29% (+3.57%)	56	36 (+2)	20 (-2)	👍

Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code.

Changed unit test files

• github.com/cobaltcore-dev/openstack-hypervisor-operator/internal/controller/decomission_controller_test.go
• github.com/cobaltcore-dev/openstack-hypervisor-operator/internal/controller/gardener_node_lifecycle_controller_test.go

[notandy]

LGMT, I also like to use Positive = True Conditions - having Conditions only false if they signal a transient state.