Fix inspecting of nested STL containers.

The problem is that GDB MI shows no children for dynamic STL objects,
it just add "dynamic" attribute to it. Here is -var-list-children
output for std::map< int, std::vector<std::string> > object:

SEND: "-var-list-children --thread 1 --frame 0 --all-values "var1" 0 5
kdevelop(20230)/kdevelop (gdb debugger) GDBDebugger::GDB::processLine:
GDB output:
"^done,numchild="2",displayhint="map",children=[child={name="var1.[0]",
exp="[0]",numchild="0",value="0",type="const int",thread-id="1"},
child={name="var1.[1]",exp="[1]",numchild="0",value="{...}",
type="std::vector<std::basic_string<char, std::char_traits<char>,
 std::allocator<char> >, std::allocator<std::basic_string<char,
std::char_traits<char>, std::allocator<char> >
> >",thread-id="1",displayhint="array",dynamic="1"}],has_more="0""

As you see, the second variable, std::vector<std::string> has
numchild="0", but dynamic="1". This patch adds extra check for
"dynamic" attribute in variables.

BUG: 330734
(cherry picked from commit 751488d07f898545c7d43af0ef1906183a4d55c3)
SVN_SILENT made messages (.desktop file)
QtHelp: Don't mark as changed if nothing happened

(cherry picked from commit 18b07ff8fc68a77409da95bb87ba409f543d2daf)
Icon fixes
GDB: Handle missing 'original-location' gracefully

Tested with GDB as of version 7.7 (released in 2014, Jan).
We may not have the 'original-location' field in all cases.
This happened when "catch throw" was used in gdbinit.

TODO: Check what we can do in case we don't get a source location at
all. Currently we might end up having empty lines in the breakpoint
table.

@Vlas, please review
Merge remote-tracking branch 'origin/4.6'

Conflicts:
	debuggers/gdb/breakpointcontroller.cpp
Remove dead code

Doesn't look like this code is going to be revived any time soon. We
have a proper coloring mechanism in place.
Remove more dead code
Include path dialog: Integrate folder browser

Thanks to Meenakshi Khorana for the initial patch

BUG: 221792
REVIEW: 113815