Remove OwnerReference dependency between Endpoint and BMC

[coderabbitai]

Summary

Remove the OwnerReference relationship currently established between Endpoint and BMC resources.

Rationale

With the Endpoint resource now deprecated (see PR #1019 and issue #1018) in favor of modeling endpoint information inline via BMC.spec.access, the existing OwnerReference from BMC to Endpoint (or vice versa) creates an unwanted side effect: Kubernetes garbage collection (GC) will delete the BMC object and all its dependent resources whenever the owning Endpoint is deleted. This is undesirable going forward since Endpoint is being phased out and should not be able to cascade-delete BMC and downstream objects.

Affected areas

• Controllers/reconcilers that set the OwnerReference between Endpoint and BMC (likely in internal/controller for the BMC/Endpoint reconciliation logic).
• Any related webhook or validation logic in internal/webhook/v1alpha1.

Acceptance criteria

• BMC objects no longer carry an OwnerReference pointing to their associated Endpoint.
• Deleting an Endpoint no longer triggers garbage collection of the associated BMC and its subsequent objects.
• Existing tests are updated/added to verify that deleting an Endpoint does not cascade-delete the BMC.

References

• PR: Deprecate the Endpoint resource #1019
• Comment: Deprecate the Endpoint resource #1019 (comment) (requested by @afritzler)
• Related issue: Deprecate the Endpoint Resource #1018

Requested by: @afritzler

[coderabbitai]

🔗 Related PRs

#599 - Improved internal code structure of the bmc package [merged]
#712 - Ensure ServerMaintenance is removed when performing a BMC version upgrade [merged]
#864 - Remove deprecated ServerMaintenanceApprovalKey and backward-compatibility logic [merged]
#885 - Remove deprecated APIVersion, Kind, and UID fields from ObjectReference types [merged]
#1019 - Deprecate the Endpoint resource [open]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!