Update README to use ratatui

[kdheepak]

In my opinion, this change in the docs will be a better user experience for most people, for the following reasons:

• With breaking changes users can't just do this to upgrade from tui:

[dependencies]
tui = { package = "ratatui", version = "0.23.0", features = ["all-widgets"]} # will cause errors because of breaking changes going forward

At best, we should only recommend this:

[dependencies]
tui = { package = "ratatui", version = "0.19.0", features = ["all-widgets"]}

But I think we should save that for the docs or the ratatui-book; and the README should have one obvious way for newcomers to add the ratatui crate to their project.

• Third party crates linked have migrated from tui to ratatui.

• If users use ratatui explicitly in the code, it'll will allow for searching for ratatui on github / gitlab etc to be easier going forward.

[codecov]

Codecov Report

Merging #446 (905fe7a) into main (3f781ca) will not change coverage.
The diff coverage is n/a.

❗ Current head 905fe7a differs from pull request most recent head ff7d496. Consider uploading reports for the commit ff7d496 to get more accurate results

@@           Coverage Diff           @@
##             main     #446   +/-   ##
=======================================
  Coverage   90.42%   90.42%           
=======================================
  Files          40       40           
  Lines       11079    11079           
=======================================
  Hits        10018    10018           
  Misses       1061     1061           

[orhun]

+1

[Valentin271]

+1 too

[joshka]

@kdheepak looks like your gpg signing was broken. Pushing a rebase should in theory allow this to merge.

[kdheepak]

Thanks for catching that! It looks like I'll need to set up a post-commit gpg signing check :)