Like named PDS members enhancement

[pujal0909]

What It Does

When copying PDSs, if the source and target have like-named members, the default behavior now is to prompt the user to confirm before overwriting the members contents (when the safe-replace option is not set to true). If the user uses the replace flag, it bypasses the prompt.

How to Test

1. Copy a source PDS into a target PDS, with both having members with the same names.
2. Notice that a prompt appears where you can select 'y/N'
3. Now copy the same source PDS into the same target PDS with the replace option.
4. Notice that the prompt is skipped

Review Checklist
I certify that I have:

• tested my changes
• added/updated automated tests
• updated the changelog
• followed the contribution guidelines

Additional Comments

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.37%. Comparing base (9340db9) to head (059e305).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2427   +/-   ##
=======================================
  Coverage   91.36%   91.37%           
=======================================
  Files         639      639           
  Lines       18283    18301   +18     
  Branches     3923     3853   -70     
=======================================
+ Hits        16704    16722   +18     
  Misses       1577     1577           
  Partials        2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

📅 Suggested merge-by date: 2/18/2025

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud