ds: Show error for unsaved dataset rename; use mtime in ms for DS entries

[traeok]

Proposed changes

For USS, we show an error if you go to rename a file or parent folder with unsaved changes. I've added this logic to the data sets tree for consistency.

This also changes data set mtime updates from the mainframe be set in milliseconds. This might avoid accidental conflict detection by VS Code as described in #3310.

Release Notes

Milestone: 3.1.0

Changelog:

• (API) Fixed issue where modification time updates to data set resources were saved in seconds rather than milliseconds since epoch.
• (ZE) Fixed an issue where renaming a data set with unsaved changes did not cancel the rename operation. Now, when renaming a data set with unsaved changes, you will be prompted to resolve them before continuing

Types of changes

• 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

• I have read the CONTRIBUTOR GUIDANCE wiki
• All PR dependencies have been merged and published (if applicable)
• A GIF or screenshot is included in the PR for visual changes
• 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

• There is coverage for the code that I have added
• I have added new test cases and they are passing
• 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.
• These changes may need ported to the appropriate branches (list here):

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.07%. Comparing base (66f4592) to head (a529d1c).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3326      +/-   ##
==========================================
+ Coverage   93.03%   93.07%   +0.04%     
==========================================
  Files         116      116              
  Lines       12094    12109      +15     
  Branches     2740     2744       +4     
==========================================
+ Hits        11252    11271      +19     
+ Misses        841      837       -4     
  Partials        1        1              

☔ View full report in Codecov by Sentry.
📢 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

[github-actions]

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

[anaxceron]

Made a suggestion for the changelog

[anaxceron]

Great changelog!

[t1m0thyj]

LGTM, thanks @traeok!