fix(v2): Update migrated and recalled data sets in tree

[traeok]

Proposed changes

Fixes the following issues:

• Fixed an issue where a migrated data set is unusable after it is recalled through Zowe Explorer
• Fixed an issue where a recalled PDS is expandable after it is migrated through Zowe Explorer
• Fixed an issue where data set nodes did not update if migrated or recalled outside of Zowe Explorer

Release Notes

Milestone: 2.18.1

Changelog:

• Fixed an issue where a migrated data set is unusable after it is recalled through Zowe Explorer. #3294
• Fixed an issue where a recalled PDS is expandable after it is migrated through Zowe Explorer. #3294
• Fixed an issue where data set nodes did not update if migrated or recalled outside of Zowe Explorer. #3294

Types of changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] Enhancement (non-breaking change which adds or improves functionality)
• [ ] Breaking change (a change that would cause existing functionality to not work as expected)
• [ ] Documentation (Markdown, README updates)
• [ ] Other (please specify above in "Proposed changes" section)

Checklist

General

• [x] I have read the CONTRIBUTOR GUIDANCE wiki
• [x] All PR dependencies have been merged and published (if applicable)
• [ ] A GIF or screenshot is included in the PR for visual changes
• [x] The pre-publish command has been executed:
  • v2 and below: yarn workspace vscode-extension-for-zowe vscode:prepublish
  • v3: pnpm --filter vscode-extension-for-zowe vscode:prepublish

Code coverage

• [x] There is coverage for the code that I have added
• [x] I have added new test cases and they are passing
• [x] I have manually tested the changes

Deployment

• [ ] I have added developer documentation (if applicable)
• [ ] Documentation should be added to Zowe Docs
  • If you're an outside contributor, please post in the #zowe-doc Slack channel to coordinate documentation.
  • Otherwise, please check with the rest of the squad about any needed documentation before merging.
• [x] These changes may need ported to the appropriate branches (list here): main (WIP)

[traeok]

"1 New Issue" is an existing problem with ZoweDatasetNode complexity. This should be resolved separately.

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 96.96970% with 1 line in your changes missing coverage. Please review.

Project coverage is 93.37%. Comparing base (a5a0cd7) to head (38208d1).

Files with missing lines	Patch %	Lines
...kages/zowe-explorer/src/dataset/ZoweDatasetNode.ts	96.55%	1 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## v2-lts #3333 +/- ## ========================================== + Coverage 93.36% 93.37% +0.01% ========================================== Files 105 105 Lines 11092 11109 +17 Branches 2426 2452 +26 ========================================== + Hits 10356 10373 +17 Misses 735 735 Partials 1 1 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[sonarcloud[bot]]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarQube Cloud

[github-actions[bot]]

📅 Suggested merge-by date: 12/4/2024

[traeok]

Had a chance to test this and it seems to work well.

All things considered, LGTM! 😋

From an internal conversation 😋

The migration request is sent and the icon changes automatically (which could technically be wrong 😅) If I do the same dataset search, I still see it there (not-migrated) But that's just because of how migration/archival schedulers may be configured.

Thanks for testing Fernando and sorry for quickly dismissing your review 😅 I've addressed the behavior you mentioned where the icon changes right away. Now, we won't change the icon and we'll wait for it to be reflected when listing data sets.

[traeok]

Should we update the version of imperative/cli to get the updated cross-spawn 😋

LGTM! 😋

Once zowe-cli#2374 is merged, I'll bump the SDK/imperative versions in this PR 😁

[zFernand0]

Should we update the version of imperative/cli to get the updated cross-spawn 😋 LGTM! 😋

Once zowe-cli#2374 is merged, I'll bump the SDK/imperative versions in this PR 😁

probably have to wait for the new cli version to be on public npm (tomorrow 🙏 )