Should the leak be reported when the object is passed to QApplication::postEvent?

Make test for usage of different variants of postEvent more robust.

apply all suggestions

Replace 'endswith' with 'operator==', also update test to check that all four ways to call postEvent not produce warning

mistype, actually I want to use '&&' here, not '||' to not create std::string,
if match failed.

Fix line length issue

I reduce testcase to almost minimal variant.

I added test case and move it to separate file, because of
1)it require additional option -analyzer-checker=cplusplus to trigger warning
2)Simple emulation of qt type system not work (not trigger any warning), so I add preprocessored file.