QtCreator above 4.8 version is utilizing a so called "compilation database" which placed in the compile_commands.json and contains generated information.

For template rules (modern style) in Qt project file,
this file is autogenerated by qmake.

Example old style (pro file):
SOURCES += src/1.cpp \
           src/2.cpp

Example new style, uses template rules (pro file):
SOURCES += src/*.cpp

qmake auto generate files with list of objects
object_script.*.Debug
object_script.*.Release

This file is autogenerated by qmake for run auto(unit) tests.
For Windows: target_wrapper.bat
For Unix: target_wrapper.sh

This file is autogenerated by qmake. It imports static plugin classes for
static plugins specified using QTPLUGIN and QT_PLUGIN_CLASS.<plugin> variables.

This file is autogenerated for static build

In some cases Qt Creator will create a CMakeLists.txt.user file with a short hash which should also be ignored. For example:

    CMakeLists.txt.user.1fa15d5

Qt generates build files for me that are `build-Projname-WhateverWhatever` so this change continues to support *-build-* folders as well as others.

- Ignore '*.moc' files (foo.moc created when foo.cpp contains a Q_OBJECT.)
- Ignore '/.qmake.cache' and '/.qmake.stash' as does the official Qt Creator project.

moc automatically generates "ui_*.h" files for each *.ui file.
Since they are auto-generated I assume they should be ignored.

Signed-off-by: Alexey Brodkin <alexey.brodkin@gmail.com>

With "CONFIG=debug_and_release" qmake generates both Makefile.Debug and
Makefile.Release. And I assume it is useful to have all types Makefiles
ignored.

Signed-off-by: Alexey Brodkin <alexey.brodkin@gmail.com>