Make Pepper work out-of-process in the windows sandbox

Make Pepper work out-of-process in the windows sandbox

Fixes the following issues
- Propper sandbox lockdown
- Rand support and the Pepper module now load
- Pipe creation failed
- Specific sandbox policy crafted for pepper
- Can now debug child process

Note, the example plugin manages to draw at least a frame, then it
crashes in some other unrelated bug.

To test use chrome with:
--register-pepper-plugins="<blah>\ppapi_example.dll;application/x-ppapi-example" --ppapi-out-of-process

And can use --ppapi-startup-dialog, which hangs until you connect the debugger


BUG=none
TEST= see above. 
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=84520

[brettw, 2011-05-06 04:30:52]

LGTM

http://codereview.chromium.org/6930059/diff/1/content/ppapi_plugin/ppapi_plug...
File content/ppapi_plugin/ppapi_plugin_main.cc (right):

http://codereview.chromium.org/6930059/diff/1/content/ppapi_plugin/ppapi_plug...
content/ppapi_plugin/ppapi_plugin_main.cc:19: sandbox::TargetServices*
g_target_services;
It's weird you initialize the void* below and not this one. Maybe write = NULL/0
here too?

http://codereview.chromium.org/6930059/diff/1/content/ppapi_plugin/ppapi_thre...
File content/ppapi_plugin/ppapi_thread.cc (right):

http://codereview.chromium.org/6930059/diff/1/content/ppapi_plugin/ppapi_thre...
content/ppapi_plugin/ppapi_thread.cc:27: extern void* g_target_services = 0;
Don't initialize extern.