Enable DOM_STORAGE in our build.

Enable DOM_STORAGE in our build.  Put LocalStorage and SessionStorage behind their own flags.  Add the beginnings of StorageNamespaceProxy since it implements WebCore::StorageNamespace::____StorageNamespace and we'd get link errors otherwise.--enable-local-storage and --enable-session-storage are the new flags.  If you enable them and try to use DOM Storage, Chromium will crash.Originally Committed in http://src.chromium.org/viewvc/chrome?view=rev&revision=21059 but then backed out due to include path issues.BUG=4360
TEST=none

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=21157

[jorlow, 2009-07-18 22:23:14]

I had to revert this CL when I checked it in because there's some issue with the
build paths on the build bots.  Any file that "#include "Storage.h"" (in webcore
and the webkit api) failed because it included some visual studio version of the
file.

In theory, this should be exactly the same as what was just reverted.

[darin (slow to review), 2009-07-19 03:54:38]

LGTM

When I need to revert a revert, I just literally do that :-)  That way, I'm
assured that it is the exact same CL and there is nothing more for anyone to
review anyways.

[jorlow, 2009-07-19 18:46:00]

On 2009/07/19 03:54:38, darin wrote:
> LGTM
> 
> When I need to revert a revert, I just literally do that :-)  That way, I'm
> assured that it is the exact same CL and there is nothing more for anyone to
> review anyways.

I tried to revert the revert.  Unfortunately, I don't think the revert script
understands how to add files back in.  Normally, that's what I'd do though.