Small improvements to rich progress bar

[SeanNaren]

What does this PR do?

Related #9547

Use exposed functions from Rich instead of the context manager. Also fixes a few signatures!

Before submitting

• Was this discussed/approved via a GitHub issue? (not for typos and docs)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• Did you make sure to update the documentation with your changes? (if necessary)
• Did you write any new necessary tests? (not for typos and docs)
• Did you verify new and existing tests pass locally with your changes?
• Did you list all the breaking changes introduced by this pull request?
• Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

• Is this pull request ready for review? (if not, please submit in draft mode)
• Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

Make sure you had fun coding 🙃

[codecov]

Codecov Report

Merging #9579 (bc70bc0) into master (8f1c855) will decrease coverage by 4%.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master   #9579    +/-   ##
=======================================
- Coverage      93%     89%    -4%     
=======================================
  Files         179     179            
  Lines       15317   15317            
=======================================
- Hits        14208   13590   -618     
- Misses       1109    1727   +618     

[tchaton]

LGTM ! But I am bit concerned about the double refresh parameters. Not sure how this would play.

[SeanNaren]

Thanks for checking this out! Just holding off on this PR till @kaushikb11 has a chance to work through the double refresh. I think the point of the refresh was for performance/logging (I assume) so just need to make sure this aligns.

[SeanNaren]

Logic has been simplified, exposing just the rich progress bar refresh rate. I've verified that the progress bar works out of the box on google colab/jupyter notebook so the additional progress bar logic for TQDM is not required