Task-number: QTCREATORBUG-1292

* Fix cv qualifiers being placed incorrectly.
* Fix nested pointer to array to pointer being printed incorrectly.
* Add autotest.

Task-number: QTCREATORBUG-1037

Done with: erikv

It introduced at least one new crash to do with recovering from parsing
errors.

Reviewed-by: Roberto Raggi

Task-number: QTCREATORBUG-807

Main reason is that find-usages and refactoring broke completely.
Second reason is that concurrent modification was done on the
children-list while deleting/destructing.

This reverts commit b0b95f88.

Patch by: Bill King

Done-with: Roberto Raggi

Fixed crash in FindUsages on a dirty file in a large project, which is saved
while the FindUsages is still running.

Fixes QTCREATORBUG-787

Reviewed-by: Erik Verbruggen

Task-number: QTCREATORBUG-577

call of overloaded ‘QString(int)’ is ambiguous

This reverts commit 2a59d2ae.

This reverts commit f4163b8b.

Because apparently, while designing the Objective-C language, somebody
thought it was a world-class idea to allow any white-space between the
'@' character and the subsequent keyword. With this fix, we now
correctly parse:
    @  dynamic
and:
    @
      selector
and:
    @"foo"
     "bar"
    @"mooze"
(This last one is 1 single string split over multiple lines.)
Wonderful, isn't it?

What we (and Clang) do not support, but what GCC supports is something
like:
   @"foo"@@  "bar"  @"mooze"  @@
which is equivalent to @"foobarmooze".