…arted from multiple threads / concurrently)

 - defaults to "single line" behavior when terminal does not support moving cursor
 - using ScheduledThreadPoolExecutor with single daemon thread (that does not prevent the JVM from exiting)
   - simplifies thread-safety and ensures only single thread is moving cursor

 - moving cursor up/down only based on the fact how many active progress bars are currently being rendered (instead of getting current cursor position in order to attempt to "re-render" correct line in console - which breaks instantly on terminal re-size)

 - no need for entering terminal raw mode (needed when asking terminal for cursor position)
 - basic terminal info (width / cursor movement support) are now public - helps when writing custom ProgressBarConsumer

…e consumer

  - currently was not the case and could cause display issue in terminals without cursor movement support (when multiple progress bars were started in parallel)
    - as the final "new line" was being writen to PrintStream from different thread
- other refactorings

 - ensure new terminal is not created on every progress bar re-render
 - at the same time ensure only single instance of Terminal was build
   - every ProgressBar can't hold instance of Terminal, although it's possible to create multiple instances of Terminal, subsequent instance are created as "dumb" until the first instance is closed