reduce the restriction on when the "inProgress" CRD BIOS/BMC Version/Settings can be updated/deleted

[nagadeesh-nagaraja]

today we stop updating/deleting CRD (BIOS/BMC Settings/Version) when the state is InProgress. this can be relaxed, to check for if the state has progressed to serverMaintenance approved.

As in many cases, the Controller is just waiting for approval and next spc update comes or object is block for deletion even though CRD/ controller is ideal and doing nothing.

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• BMCVersion/Settings and BIOSVersion/Settings get stuck at InProgress state #416

🔗 Related PRs

#581 - Transition Server to Maintenance in case of pending BIOS settings exist [merged]
#744 - Improve deletion logic in of BMC* and BIOS* types [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!