when I attempted to implement a way how to control dump details level
more precisely, I run into problems, since throughout the ages, we
devised various clever ways how to (miss)use dump files. This patch
attempts to clean up it a bit. It ensures that (up to a few exceptions),
the following rules are observed:
1) All the dumps go to dump_file, directly using the global variable
(in several passes, we were either passing dump_file around in
arguments, or assigned it to a local static variable, or even used
a higher level of magic -- see e.g. profile_dump_file).