Move html progressbar

[HarshKhilawala]

Checklist
Thank you for contributing to QuTiP! Please make sure you have finished the following tasks before opening the PR.

• Please read Contributing to QuTiP Development
• Contributions to qutip should follow the pep8 style.
  You can use pycodestyle to check your code automatically
• Please add tests to cover your changes if applicable.
• If the behavior of the code has changed or new feature has been added, please also update the documentation in the doc folder, and the notebook. Feel free to ask if you are not sure.
• Include the changelog in a file named: doc/changes/<PR number>.<type> 'type' can be one of the following: feature, bugfix, doc, removal, misc, or deprecation (see here for more information).

Delete this checklist after you have completed all the tasks. If you have not finished them all, you can also open a Draft Pull Request to let the others know this on-going work and keep this checklist in the PR description.

Description
Moved HTMLProgressBar from qutip/ipynbtools.py to qutip/ui/progressbar.py

Related issues or PRs
Fix #2108

[HarshKhilawala]

@Ericgig Please review the PR.Thanks!

[HarshKhilawala]

@AGaliciaMartinez Can you please review this PR and get it merged?

[hodgestar]

The change itself looks good. I left one small suggestion. I've also activated the test runs, so we should see if those pass.

It would be good to add tests for the progress bars, but perhaps that is best done in a follow up PR. For example, I know that the TqdmProgressBar currently does not work.

[coveralls]

Coverage: 72.089%. Remained the same when pulling 8de851f on HarshKhilawala:move-html-progressbar into c499d44 on qutip:master.

[HarshKhilawala]

@hodgestar PTAL! Thanks

[hodgestar]

Thanks @HarshKhilawala!

[hodgestar]

@HarshKhilawala Would you be interested in adding some tests for the progress bars in another PR?

[HarshKhilawala]

@hodgestar Sure, do I need to be assigned another issue? Can I create new issue for writing tests for progress bar and get assigned to work on it?

[hodgestar]

No need for a new issue. You can just open a PR. No harm in having an issue too though.

[HarshKhilawala]

@hodgestar I am not much aware with writing tests. Can you help me write test for progressbar file? How to write a test? How to check coverage for the entire file? How to check coverage for each line of code as to know where and what to add test? From where can I learn more about testing? Any documentation for writing tests specifically for qutip repository?

[HarshKhilawala]

@hodgestar Anything for reference? Any pre-existing test_code which I can use to write tests for progressbar? PTAL!

[HarshKhilawala]

@Ericgig Can you help me with this one? I am considering adding tests for progressbar.

[Ericgig]

There are no test code for progress bars yet.
You will need to create a new test file: qutip/tests/test_progressbar.py.

The test can be as simple as creating the bar, call update, call finished and check that the total time is a sensible value.
You could also use pytest to catch print with capsys and confirm that something was printed when update / finished is called.