The Sail Operator CI configurations across different OCP versions (4.18, 4.19, etc.) contain significant code duplication for common operations like source copying, e2e test execution, and upstream syncing. This duplication makes maintenance difficult and error-prone when updates are needed across multiple job configurations.

Solution:
Create reusable step registry entries to standardize and parameterize common CI operations, eliminating code duplication and improving maintainability. This is already being used in the prow jobs configurations for other teams

Acceptance Criteria

• Step Registry Implementation, adding the configuration, definition, and bash script
• Job Configuration Updates: update all the configuration jobs to use these new steps
• Functionality Preservation: It should continue working as it is working now
• Maintainability Improvements: It should be easier to maintain
• Security Enhancements: ensure that no sensitive information is logged in CI output