Fix for security exception binding to a process in MonoChrome.

When we start the moderate binding management, we were using a null
ChildProcessCreationParams when retrieving the ChildConnectionAllocator.
If there was no allocator allocated, one would be created but with false
for isExternalService, causing the next allocated sandboxed processes to
fail to bind.

BUG=730765

Change-Id: I2d57b07cb642cf8296245e0d14632bb963972bfa
Reviewed-on: https://chromium-review.googlesource.com/531836Reviewed-by: Bo Liu <boliu@chromium.org>
Commit-Queue: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#478836}

content/public/android/java/src/org/chromium/content/browser/ChildProcessLauncherHelper.java

@@ -231,7 +231,7 @@ public class ChildProcessLauncherHelper {
             @Override
             public void run() {
                 ChildConnectionAllocator allocator = getConnectionAllocator(
-                        context, null /* creationParams */, true /* sandboxed */);
+                        context, ChildProcessCreationParams.getDefault(), true /* sandboxed */);
                 getBindingManager().startModerateBindingManagement(
                         context, allocator.getNumberOfServices());
             }