MSVC 2010+ Projects: Update "Installation" Process

Currently, due to the way that Visual Studio 2010+ projects are handled,
the "install" project does not re-build upon changes to the sources, as it
does not believe that its dependencies have changed, although the changed
sources are automatically recompiled.  This means that if a part or more
of the solution does not build, or if the sources need some other fixes
or enhancements, the up-to-date build is not copied automatically, which
can be misleading.

Improve on the situation by forcing the "install" project to trigger its
rebuild, so that the updated binaries can be copied.  This does trigger an
MSBuild warning, but having that warning is way better than not having an
up-to-date build, especially during testing and development.
Updated German translation
Build: Add Build Support for Visual Studio 2013

Like the Visual Studio 2012 projects, the Visual Studio 2013 project files
are only slightly different from the Visual Studio 2010 files, in more or
less the same manner.  We can thus easily provide out-of-box support for
building under Visual Studio 2013 by expanding on the scripts used to
provide support for the Visual Studio 2012 projects, without adding much
maintainance overhead.
MSVC 2012/2013 Support: Update Property Sheet Creation

Be a bit more careful when copying and updating the property sheets, so that
we don't accidently change fields with '10' in them that are actually not
indicating the Visual Studio version.
Release 2.13.2
Release 2.13.3
Give CC to gir scanner

Change needed by the MINGW project.

Signed-off-by: Alejandro Piñeiro <apinheiro@igalia.com>