BREAKING(cli/unstable): make ProgressBar value and max properties public

[timreichen]

Ref: #6408 (comment)

This PR makes the ProgressBar value and max properties public.
This is more flexible as the progress bar max can be adjusted after instantiation and allows to set the value directly (progressBar.value = newValue) instead of only adding increments.
This makes the add() method obsolete as the same can be achieved with progressBar.value += x.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.70%. Comparing base (ba0fc29) to head (53c02cf).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6430   +/-   ##
=======================================
  Coverage   94.70%   94.70%           
=======================================
  Files         562      562           
  Lines       46646    46646           
  Branches     6569     6569           
=======================================
  Hits        44174    44174           
  Misses       2429     2429           
  Partials       43       43           

☔ 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]

It makes sense to me to make max modifiable as I sometimes see such progress indicator (e.g. Deno's download indicator)

It also makes sense to make value public property as it now accepts the total value number in addition to the difference. (It should be convenient when the progress source only reports the total current number.)

LGTM

[kt3k]

@timreichen Thanks for updating!