Update `bytesize` from v1 to v2.

### Commit Statistics

 - 3 commits contributed to the release.
 - 0 commits were understood as [conventional](https://www.conventionalcommits.org).
 - 0 issues like '(#ID)' were seen in commit messages

### Commit Details

 * **Uncategorized**
    - Update changelog prior to release (2216036)
    - Merge pull request #33 from EliahKagan/bump-bytesize (4ff81bf)
    - Bump `bytesize` from major version 1 to 2 (61dfa7d)

### Other

 - switch from `humantime` to `jiff`
   Since prodash switched over to Jiff, Jiff has grown support for the
   "friendly" duration format. It is meant to be a replacement for
   `humantime` formatting of durations.
 - bump jiff to 0.2

### Commit Statistics

 - 5 commits contributed to the release.
 - 2 commits were understood as [conventional](https://www.conventionalcommits.org).
 - 0 issues like '(#ID)' were seen in commit messages

### Thanks Clippy

[Clippy](https://github.com/rust-lang/rust-clippy) helped 1 time to make code idiomatic. 

### Commit Details

 * **Uncategorized**
    - Merge pull request #32 from BurntSushi/ag/moar-jiff (eaf1c26)
    - Thanks clippy (521c6e1)
    - Switch from `humantime` to `jiff` (88d3399)
    - Bump jiff to 0.2 (373b6b1)
    - Remove unused feature (9c476cf)

### Chore

 - update ratatui to 0.26.0
   Requires an update to tui-react / crosstermion to work

### Other

 - switch from `time` to `jiff`
   This swaps out `time` in favor of `jiff` for getting and formatting the
   local time.
   
   Note that this does add the `%Z` to the format string, which will write
   out time zone abbreviations like `EDT` along with the local datetime
   itself. The `time` crate doesn't support this, but jiff's tzdb
   integration let's it do it.

### New Features (BREAKING)

 - upgrade `ratatui` to v0.26

### Commit Statistics

 - 8 commits contributed to the release over the course of 177 calendar days.
 - 213 days passed between releases.
 - 3 commits were understood as [conventional](https://www.conventionalcommits.org).
 - 0 issues like '(#ID)' were seen in commit messages

### Commit Details

 * **Uncategorized**
    - Upgrade dependencies (a5dab6e)
    - Merge branch 'ag/jiff' (87f66fb)
    - Switch from `time` to `jiff` (aab0986)
    - Fix CI (10800f3)
    - Upgrade `ratatui` to v0.26 (f3c3122)
    - Avoid running benchmarks on CI for faster runs (73bce79)
    - Update to latest versions of `tui-react` and `crosstermion` (0cca41f)
    - Update ratatui to 0.26.0 (5f066f2)

### Chore (BREAKING)

 - upgrade `ratatui` and `crosstermion` to latest versions.

### Commit Statistics

 - 1 commit contributed to the release.
 - 21 days passed between releases.
 - 1 commit was understood as [conventional](https://www.conventionalcommits.org).
 - 0 issues like '(#ID)' were seen in commit messages

### Commit Details

 * **Uncategorized**
    - Upgrade `ratatui` and `crosstermion` to latest versions. (18686db)

### New Features

 - Change duration formatting to be more human readable.
   Note that this changes duration output from something like `69d10h40m`
   to `69d 10h 40m`.

### Reverted (BREAKING)

 - All `termion`-related features are now removed and obsolete.
   After the most recent update, certion event-related features in crosstermion
   stopped working in the context of the GUI, so it's probably best to let it go.
   
   By now, `crosstermion` is also very much a more portable replacement.

### Commit Statistics

 - 7 commits contributed to the release over the course of 44 calendar days.
 - 89 days passed between releases.
 - 2 commits were understood as [conventional](https://www.conventionalcommits.org).
 - 0 issues like '(#ID)' were seen in commit messages

### Thanks Clippy

[Clippy](https://github.com/rust-lang/rust-clippy) helped 1 time to make code idiomatic. 

### Commit Details

 * **Uncategorized**
    - Merge branch 'replace-ansi_term' (3a50a18)
    - All `termion`-related features are now removed and obsolete. (b1fd37d)
    - Thanks clippy (3c28eb0)
    - Upgrade to `crossterm` v0.27. (34397f1)
    - Change duration formatting to be more human readable. (6acf6fe)
    - Refactor (d032106)
    - Replace compound_duration with humantime This is the humantime part of PR #25 (f5143c9)

This release relaxes trait-bounds of `Count`, `Progress` and `NestedP…

…rogress` to allow `?Sized` as well.

### Commit Statistics

 - 4 commits contributed to the release.
 - 2 days passed between releases.
 - 0 commits were understood as [conventional](https://www.conventionalcommits.org).
 - 0 issues like '(#ID)' were seen in commit messages

### Commit Details

 * **Uncategorized**
    - Prepare next release (414506d)
    - Merge pull request #24 from NobodyXu/fix/dyn (c905d5c)
    - Relax bound of `Progress`, `Count` impl for `DynNestedProgressToNestedProgress` (967ea46)
    - Fix use of `DynNestedProgress` as trait object (7eb69ac)

### Bug Fixes

 - Add missing forwardings for various methods.
   Not having these could lead to incorrect thoughput display.

### Commit Statistics

 - 1 commit contributed to the release.
 - 1 commit was understood as [conventional](https://www.conventionalcommits.org).
 - 0 issues like '(#ID)' were seen in commit messages

### Commit Details

 * **Uncategorized**
    - Add missing forwardings for various methods. (53ea2b8)

### New Features

 - add `BoxedProgress` type that implements `Progress`.
   This makes working with boxed progress even more flexible.

### Commit Statistics

 - 1 commit contributed to the release.
 - 1 commit was understood as [conventional](https://www.conventionalcommits.org).
 - 0 issues like '(#ID)' were seen in commit messages

### Commit Details

 * **Uncategorized**
    - Add `BoxedProgress` type that implements `Progress`. (b3cae19)

### New Features

 - add `progress::AtomicStep` to allow referring to it.
   Previously, only `StepShared` was available, which implies an `Arc`.

### Commit Statistics

 - 1 commit contributed to the release.
 - 1 commit was understood as [conventional](https://www.conventionalcommits.org).
 - 0 issues like '(#ID)' were seen in commit messages

### Commit Details

 * **Uncategorized**
    - Add `progress::AtomicStep` to allow referring to it. (0705a73)

This release is all about making `dyn` possible both for nested progr…

…ess, as well as for 'simple' one (previously known as `RawProgress`).

Switching to this release naturally makes it possible for users of `Progress` to also use `dyn Progress`, as this trait is now object safe (formerly `RawProgress`).
If there are compile errors, the code now needs `NestedProgress`, instead of `Progress`, and possibly the import of the `Count` trait.
Finally, it's recommended to review all usages of `Progress` as they can possibly be replaced with `Count` which provides the guarantee that only counting happens,
and no change of the progress information itself.

### New Features (BREAKING)

 - split `Progress` into various super-traits to allow most of them to be dyn-safe.
   `Progress` is now `NestedProgress`, `RawProgress` is now `Progress`, and there is
   a new `Count` trait for solely counting things.
 - `Progress::counter()` is now mandatory.
   This should simplify downstream code and we just accept that we are dealing
   with a threaded world.
   This also comes with performance improvements as increments are now 250% faster.

### Commit Statistics

 - 8 commits contributed to the release.
 - 13 days passed between releases.
 - 2 commits were understood as [conventional](https://www.conventionalcommits.org).
 - 0 issues like '(#ID)' were seen in commit messages

### Commit Details

 * **Uncategorized**
    - Merge branch 'simplify' (5e21df7)
    - `Progress::counter()` is now mandatory. (6c60835)
    - Prepare release (e1e282a)
    - Fixup nested dyn-traits (5e76abf)
    - Merge branch 'feat/dyn-progress' into simplify (c1590e4)
    - Split `Progress` into various super-traits to allow most of them to be dyn-safe. (6aba6e3)
    - Add benchmarks for dyn-traits (9d03124)
    - Refactor (54094b6)