zsh render issue

[valarauca]

Summery

We switch from the mpb to pb progress bar library. This fix was coupled with an implicit fix for windows render issues.

The root of the error as far as I can tell is broken zsh configurations. Sadly mpb uses 3 escape sequences to do what pb does with 1. This extra escape sequence allows for it to terminate existing escape sequences which could potentially be opened to be a bad configuration. One should be able to quick see iTerm2 + zsh + oh-my-zsh has had rough transition in MacOS Mojave as it appears some of the configuration options in zsh were very quietly broken in the transition.

Either way, backwards compatibility, and cross platform support is king so here we are.

Motivation

• https://github.com/ShiftLeftSecurity/product/issues/1942

Changes

• Added a config.go who's goal is mostly run func init() and set a few varibles
• Added a few modification to the pb_win.go to possibly offer support on mintty, cygwin, gitbash.exe doesn't work for mintty on windows cheggaaa/pb#88

Test

I'll need assistance with this if I could ask for these folks for assistance to see if this works

• @tuxology can I borrow Josh to do windows testing? If we could get screen shots of
  • powershell.exe
  • cmd.exe
  • gitbash.exe
  • cygwin
• @Preetam can you test with zsh and bash in the vanilla Terminal.app in MacOS?
• @perrito666 / @prathik23 can either you attempt to duplicate your issue in MacOS?
• @tuxology can you be a control for linux-centric zsh ?

[Preetam]

Works for me

[valarauca]

well we gained support for cygwin and mtty, but alas oh-my-zsh users are still broken.

[valarauca]

Finishing up a feature request for @perrito666 that we should pad a few new lines prior to starting to display the progress bar. This is now exposed as a configuration operation, so if PadStart string is included it'll print that before the bar is rendered.