Move WinSock initialize earlier in the startup process.  I ran into a case where my extension used the network; but because extensions are initialized earlier than WinSock init, the extension failed when trying to do a dns lookup.  This only fails because it was in conjunction with the --single-process flag, so it is unlikely to effect others.
Move WinSock initialize earlier in the startup process.  I ran into
a case where my extension used the network; but because extensions are
initialized earlier than WinSock init, the extension failed when
trying to do a dns lookup.  This only fails because it was in conjunction
with the --single-process flag, so it is unlikely to effect others.

Nonetheless, there is really no harm in moving winsock initialization
to be very early.

BUG=none
TEST=none


Review URL: http://codereview.chromium.org/454021

git-svn-id: http://src.chromium.org/svn/trunk/src@33486 4ff67af0-8c30-449e-8e8b-ad334ec8d88c

Former-commit-id: 916b2a919158d4ae410a3ff2b7004728b43d4ffd
meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser