refactor(cli/unstable): use Date.now() internally and use FakeTime for testing

[timreichen]

Ref: #6684

Seems like the random delay in setData() could lead to tests being flaky.
This PR removes the function altogether and adds additional tests.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.70%. Comparing base (55d0efb) to head (c9cd3e5).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6686   +/-   ##
=======================================
  Coverage   94.70%   94.70%           
=======================================
  Files         567      567           
  Lines       46789    46789           
  Branches     6582     6582           
=======================================
  Hits        44310    44310           
  Misses       2437     2437           
  Partials       42       42           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[kt3k]

Seems still flaky https://github.com/denoland/std/actions/runs/15269321101/job/43006417785?pr=6686

[BlackAsLight]

Since your expected results changes based on execution time, you can't have a static expected output. You're going to need something more flexible to confirm the results of the output or it will continue to appear flaky at times.

[timreichen]

I updated the ProgressBar class so it uses Date instead of performance internally, so it can be tested with FakeTime. This should give more consistent results.

[timreichen]

@kt3k Funnily enough there seems to be a flaky fs/renameSync test that fails here...

[kt3k]

LGTM