vector printing in qmcpack output

I found vector printing bloat the lines of printout and made it not readable.
Such printout includes
1. atomic/electron positions
2. wavefunction parameters. From individual components (Jastrow) and global(#5477) during initialization and WFOpt run.
3. Spherical grid and weights.

We can hide certain printout under verbosity. We still need to decide what should go to `high` or `debug`. Do we really need both levels above `low`?

I actually don't feel like printing long vectors under `debug` is helpful.
For example, when I need to make a deterministic test, I'd like to initialize electrons with fixed positions. To make a better distribution, I used one run to randomize the electron positions and then I'd like to save them and then put them back into the input xml. To see such positions, I have to rerun with debug and cut paste coordinates from the printout. Instead, I'd rather see simple `ions.position.dat` and `electrons.position.dat` files.

Similarly, many lines of parameters during optimization basically made me not willing to look at the standard output and I can potentially missing useful hints/warnings in the printout.

In summary, I feel the qmcpack output should never explode even in the "debug" mode. It is for tracking progress not for looking data. So vector printing should not be included in the QMCPACK standard output.