Refactor progress bars

[czoido]

Changelog: Feature: Refactor Conan Upload, Download and Compress progress bars.
Docs: omit
Closes #5739

• Refer to the issue that supports this Pull Request.
• If the issue has missing info, explain the purpose/use case/pain/need that covers this Pull Request.
• I've read the Contributing guide.
• I've followed the PEP8 style guides for Python code.
• I've opened another PR in the Conan docs repo to the develop branch, documenting this one.

^{Note: By default this PR will skip the slower tests and will use a limited set of python versions. Check here how to increase the testing level by writing some tags in the current PR body text.}

[CLAassistant]

All committers have signed the CLA.

[memsharded]

This is looking very, very good!
This refactor is very challenging, but excellent job here.
Please have a look to the comments.

[memsharded]

I have been thinking a bit, and I would say that the correct approach would be:

• Do not change the output.py to include tqdm stuff
• Make an Adapter around an output, that returns a similar output object, but that overwrites the write with the custom tqdm stuff. This adapter is part of the progress_bar package
• Pass adaptors around the outputs to those who need them in the context of progress bars being displayed. They shouldn't be many, I'd say that only 1 or 2 different messages are interleaved to progress bars.

This is just an idea, lets wait for @lasote feedback on this PR.

[czoido]

I like that idea and would be much safer than using it for all the output.

[lasote]

As I talked with you on Slack, probably we can unify ReadProgress and WriteProgress.
I've been trying locally and works very well. The code is much nicer too. So great work.

[memsharded]

Small question, but otherwise fantastic job, can be merged (after fixing the broken iterator: https://conan-ci.jfrog.info/blue/organizations/jenkins/ConanTestSuite/detail/PR-5763/37/pipeline)