Streamlined Change Control Workflow for Ansible-Based Runbooks

Change Control workflows today require separate 'Define Change' and 'Execute Change' tasks even when a customer uses an Ansible runbook, which already fulfills the requirements of both steps. As a result, the Ansible task is treated as a secondary validation step rather than as the core change itself. This enhancement would introduce a Change Control flow optimized for Ansible-based changes, where a single Ansible runbook task satisfies both the definition and execution requirements. Once the change is approved, the Ansible task would be locked in the same manner that the 'Define Change' task is locked today. This would simplify the change process for Ansible-oriented teams, reduce redundant steps, and align the platform's change workflow with existing automation practices.