Well this enough environment settings for 1.2.

Note: as for qt projects, this is also used for running. And we don't
use it for running cmake yet.

After all I don't need all that stuff in the cmakeplugin, all i needed
is now bundled in debugginghelper.h/cpp

Enables me to move some stuff back again.

Remove duplicated code from cmakeprojectmanager.

Task:  250418

This also moves us closer to supporting multiple build configurations
properly.

Task: 250415

Even works.

Adds a little bit of code duplication, don't currently know how to best
avoid it, so I'll leave that for now as is. To be tested once Andre
pushes his stuff.

We used to build a helper library as part of the project. First with the
qmake -after SOURCES= stuff and after until now with the
gdbmacrosbuildstep. Now, the all new and fancy integretation directtly
into the qt version dialog. You build the debugger library once for
each qt version and then it's there ready to be loaded into each
project build against that qt version. Saves a lot of time.
And makes it possible to also load that library into while debuggign a
cmake project. (Need to hook that up now.)
Unfourtanetly this breaks the custom dumpers if you use a custom run
executable.

It was missing for CustomExecutableRunConfiguration and
Qt4RunConfiguration.

Reviewed-by: dt

Made the cmake plugin even more usable by implementing:
Pop up a wizard if there is a .user file but no .cbp file. (Fixes empty
project reported on irc.)
Pop up a wizard if the .cbp file is older then the CMakeLists.txt file,
thus reparsing the file. (Note: There is a bug that we need to actually
also check the last modified of all included files.)
Reparse the cbp file to add new RunConfigurations / delete no longer
existing RunConfigurations and update those that have changed.-
Show a nicer title in the Projects/RunConfiguration pane

Details:  Not the most pressing problem, but easy to fix.

Task:     -
RevBy:    -
AutoTest: -
Details:  -