Clean up the Visual Studio 2010 projects

Use a single solution file for the non-PangoFT2 and PangoFT2 builds, and
use a single PangoCairo project for these builds too.  Also get rid of
configurations that we don't really need in the Pango and PangoWin32
projects.
build/Makefile-msvcproj.am: Cleanup

Remove lines that were left out in the last commit
pango-utils: Fix a potential strtol(NULL) call

parse_int() is called by pango_parse_enum(), which permits the enum
string to be NULL. This string is passed directly through to parse_int()
and then to strtol(), which is tagged as nonnull.

Found by scan-build.

https://bugzilla.gnome.org/show_bug.cgi?id=719549
Update config.h.win32.in

Make its entries more consistent to the autotools-generated config.h.in,
and update MODULE_VERSION to 1.8.0, as that was missed.
build/win32/vs10/pango.vcxprojin: Clean up

We don't really need to NoFCDef here, so remove that.
build/win32/vs10/pangowin32.vcxproj: Clean up

We don't really need the NoFCDef here, as this DLL has nothing to do with
FreeType, like the main Pango DLL.  FreeType matters when we build
PangoCairo (and the cxx-test.c and pango-view) though.
build/win32/vs10/pango.propsin: Improve DLL "installation"

Make the DLL installation more flexible, as one might still prefer to use
the autotools style DLL naming for the Visual Studio builds.
build/win32/vs10/pango.propsin: Fix .lib installation

Missed out the $(Platform) part when building the FontConfig flavor, so
make it up.
Cleanup the Visual Studio 2008 Project Files

Combine the non-PangoFT2 and PangoFT2 builds into one single solution file
and remove configs in the Pango and PangoWin32 projects that aren't really
necessary.  Also use Link Time Code Generation for release builds to
improve optimization a bit.
Visual Studio 2010 Projects: Improve Optimization

Turn on Whole Program Optimization/Link Time Code Generation for release
builds to improve optimization a bit
build/win32/vs*/README.txt: Update build information

As there is no longer a pango_fc.sln solution file, tell the people to use
the *_fc configs if building PangoFT2 and PangoCairo with FreeType/
FontConfig support with the Visual Studio Projects is desired.
Split up the MSVC 2008 Property Sheets

...so that the maintenance of these files would be easier
Split up the MSVC 2010 property sheets

Split up the property sheets so that their maintenance can be simplified
Remove the original "big" MSVC2010 property sheet
MSVC 2008 Projects: More cleanups

We don't have the *_FC configs in the Pango and PangoWin32 projects
anymore, so get rid of all remaining traces of them in these projects, like
the MSVC 2010 ones.