Reviewed-by: Trust Me

CONFIG+=debug_and_release not working on linux and
CONFIG-=debug_and_release not working on windows.
The logic should be now correct. That is the profile reader reads the
values that are set for the qt build, gets qmake arguments which we
might pass on the command line and reads the .pro files, and in the end
we are interested what CONFIG contains. Patch from Michael Karcher

Task-number: 254925

Done with dt.

Note: This code should be shared between Qt4RunConfiguration,
CMakeRunConfiguration and CustomRunExecutable. Also we are approaching
other IDEs like configuraion options for setting the environment.
Without having a good GUI for that. I'll probably be redesigning this
for 1.3 or 1.4.

Missing is options to base the environment on either:
- the last build buildconfiguration (current implementation)
- the project environment
- a clean environment

signals which indicate that the baseEnvironment changed
some layout stuff is wrong

Qt Creator wouldn't find the correct target if shadow building a project
that uses $$OUT_PWD, like for example itemviews-ng.
We didn't set the necessary variable on the ProFileReader *, simplified
the code to always use a ProFileReader created for the exact
profilenode.

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

Remove duplicated code from cmakeprojectmanager.

The Debugger, cmake and Qt4 plugin all need it. More refactoring to it
coming.

Save a relative path to the .pro file. This means RunConfigurations can
now be shared between platforms.
Note: BuildConfigurations have two problems: The qt version id and the
shadow build option. If the user doesn't use those two, then he is fine.

Look in the run configuration for it.

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.

Fixes issues with handling additional dots in the filename in many
places.

Task: 246390

Task:     247606
Details:  Remove all the magic which build on top of the cumalative
parser. Instead trust the exact parsing to get those variables correct.
This required a bug fix in the profile evaluator, done with ossi.
Hopefully this doesn't break windows/mac. Will check.

It was missing for CustomExecutableRunConfiguration and
Qt4RunConfiguration.

Reviewed-by: dt

RevBy:    Ossi

Task:     242513
Details:  That should fix several parsing problems for .pro files with
scopes. Enable it, see how many bug reports we get, for stuff we
accidentaly parsed correctly. Shouldn't be many. So we parse the
follwing now correctly:
unix {
    TEMP=unix
}
win32 {
    TEMP=win32
}
DESTDIR=$$TEMP

Task:     242465
Details:  connect quite a few signals. It doesn't work 100%, since it
really depends on to many things.

replace ExtensionSystem::PluginManager::instance()->getObject<Core::ICore>() by Core::ICore::instance()

forward declaration is sufficient.

Task:     Found on irc by ferret_svk
Details:  Even if CONFIG is debug_and_release we are interested wheter
          debug or release is the default.