Add “Pin Test Suite / TCER to Current Versions” (feature parity with HP ALM)

In HP ALM, Test Lab provides a “Pin” feature that freezes a Test Set to the current versions of the associated test cases. This ensures that execution uses stable versions of tests even if test authors modify the test artifacts later.
This is critical for reproducible regression cycles and stable execution during long-running test efforts.

In IBM ETM:

• Baselines are read-only and cannot be executed against directly
• Test Suites in streams cannot be pinned to a specific version snapshot
• Assigning a configuration context requires using streams or baselines, but this does not behave like ALM’s per‑suite pinning
• There is no ability to freeze a suite so that future artifact changes do not impact execution

Requested Enhancement:

Add a “Pin to Current Versions” option for:

• Test Suites
• TCERs
• Test Plans (optional)

This feature should:

1. Freeze the suite to the current versions of all referenced test artifacts
2. Ensure execution always uses these versions, regardless of ongoing edits in the stream
3. Store the pinned version IDs in the Suite/TCER metadata
4. Allow execution records to reflect that the suite was pinned
5. Enable reproducible test cycles without requiring baseline creation or multi-stream branching

Business Justification:

• Long-running regression cycles require stable, version-frozen execution
• Avoids defects caused by drifting test changes
• Reduces the need for additional streams or baselines
• Simplifies execution for testers without forcing configuration management complexity

Impact if Not Addressed:

• Testers may unintentionally execute tests using updated artifacts mid-cycle
• Regression cycles become unstable
• Organizations migrating from ALM experience loss of functionality
• Additional administrative overhead of maintaining separate streams/baselines for execution stability