Fix all tqdm.write() issues

[casperdcl]

1. rename tqdm.write to tqdm.print since it tries to do fancy end='\n'-type things
   • handle deprecation for v5
2. re-look at said fancy end logic
3. provide a real tqdm.write (perhaps called tqdm.write_str following the same naming convention as set_description_str, set_postfix_str.

Issues (moan):

• tqdm_gui.write() in the GUI instead of console? #172 pb.write and print don't work in jupyter notebook #644 in submodules (GUI and notebook mode)
• Alternative approach to redirect outputs to tqdm.write() #197 Could tqdm default to redirecting std{out,err} to tqdm.write? #296 stdout redirection issues #588 alt approaches
• end issues tqdm.write() "end" argument not working #520 tqdm.write(string) doesn't work well when string has \n in it #564
  • logging-related issues Pass progress bar to logger #313 Help with multiprocessing logging #551 tqdm + logging, message containing line feed gets eaten after line feed #724
• unexpected behaviour manual control over positioning not working when work with tqdm.write #578 tqdm.write not working as expected #683 Bad formatting when using colors and tqdm.write #692
• non-string arguments write() not printing #342 tqdm.write 'int' object has no attribute 'decode' #699
• synchronisation tqdm.write under multiprocessing.Pool make bars overlapped #680
• somehow print under closed bars tqdm.write() overwrite closed nested progress bar #719

[mauricelanghinrichs]

there is also this stackoverflow question that might be interesting for the synchronisation issue #407 and #680

[walidbou6]

when we use tqdm.write(mytext, file=myfile) it's great all text are saved in the file but can't see the prints, I think you may add a verbose option to show logs in the same time saving them to the file