Command line profiling

As we'll run more and more into performance testing, standardizing the way we collect and curate profiling traces across the board will become crucial. Since some of this profiling will be performed on remote machines, a requirement on JVisualVM is certainly overkill.
This PR makes a simple proposal: having a `BF_PROFILE` flag for command-line tools which enables `hprof` profiling and outputs an `.hprof` file to be examined via GUI tools.

Couple of remarks/questions at this point:
- is `hprof` the best candidate here? see http://www.brendangregg.com/blog/2014-06-09/java-cpu-sampling-using-hprof.html for a discussion and I know @joshmoore had other ideas
- where is the best place for documenting this (as well as other command-line tools environment variables), I started working on `users/comlinetools/index.txt` but then wondered wether we should not have a developers page for these features /cc @hflynn
This also doesn't set the profiling depth quite right if ```BF_PROFILE_DEPTH``` is empty.  ```setlocal enabledelayedexpansion``` needs to be added in line 2 of ```bf.bat```, and then the ```%BF_PROFILE_DEPTH%``` on line 36 (and only line 36!) needs to be replaced with ```!BF_PROFILE_DEPTH!```.  Completely annoying, but otherwise the depth of 30 will never stick.

See http://superuser.com/questions/78496/variables-in-batch-file-not-being-set-when-inside-if