Goal: 
As an infrastructure operator using Redfish-based hardware, I want to run inspection operations on nodes that are actively serving workloads. So that I can gather hardware inventory and status information without requiring node downtime.

Currently, Ironic restricts inspection operations to inactive nodes to avoid impacting running workloads. However, Redfish provides out-of-band management capabilities that allow hardware inspection without affecting the node's active workload. This restriction is unnecessarily limiting for Redfish-based deployments.

Acceptance Criteria:

1. Redfish inspection interface can successfully inspect nodes in `active` state
2. Inspection operations are performed entirely out-of-band without impacting the running workload
3. Other drivers (non-Redfish) continue to respect the existing restriction for inactive nodes only
4. Appropriate logging indicates when inspection is performed on an active node
5. Documentation is updated to reflect this capability for Redfish drivers
6. Existing inspection validation logic is updated to allow Redfish drivers to bypass the active state restriction

Technical Notes

• This enhancement should be driver-specific (Redfish-only initially)
• The inspection interface may need a driver capability flag to indicate support for active-node inspection
• Consider microversion requirements if this changes the API behavior
• Ensure proper error handling if out-of-band inspection fails on active nodes

Reference:

1. Launchpad Bug: https://bugs.launchpad.net/ironic/+bug/2138129