Add ApplyResultEntry type to BMCSettings status for persisting ETag metadata

[atd9876]

Description

Add the ApplyResultEntry type to BMCSettingsStatus so the controller can persist ETag metadata from successful apply operations. This enables ETag-based drift detection in subsequent reconcile loops without re-reading every attribute value.

Changes

1. Add AppliedETags map[string]ApplyResultEntry field to BMCSettingsStatus

2. Define the ApplyResultEntry struct:

   ```go
   type ApplyResultEntry struct {
   URI string json:"uri,omitempty"
   ETag string json:"etag,omitempty"
   ValueHash string json:"valueHash,omitempty"
   }
   ```

   • URI: the Redfish resource URI from the apply response
   • ETag: the ETag captured after successful apply
   • ValueHash: SHA-256 hash of the effective value at apply time (detects desired-state changes from ConfigMap/Secret rotation)

3. Regenerate CRD manifests and deepcopy code (make manifests generate)

Files

• api/v1alpha1/bmcsettings_types.go
• api/v1alpha1/zz_generated.deepcopy.go (generated)
• api/v1alpha1/applyconfiguration/api/v1alpha1/applyresultentry.go (generated)
• api/v1alpha1/applyconfiguration/api/v1alpha1/bmcsettingsstatus.go (generated)
• api/v1alpha1/applyconfiguration/internal/internal.go (generated)
• api/v1alpha1/applyconfiguration/utils.go (generated)
• config/crd/bases/metal.ironcore.dev_bmcsettings.yaml (generated)

Acceptance Criteria

• make manifests generate produces clean output
• make test green
• CRD validates with kubectl apply --dry-run=server
• No controller logic changes — this is purely the API type addition

[coderabbitai]

🔗 Related PRs

#673 - Use Header.Get("ETag") instead of accessing Header map directly [merged]
#723 - Simplify BMCSettings reconciler and fix bugs [merged]
#746 - Add support for dynamic BMC settings in BMCSettingsSet type [merged]
#861 - Rework condition handling during settings application and BMC reset [merged]
#902 - BMC Settings Spec to support display names for enum typed settings attributes for Dell [merged]

---

📝 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!