chore: don't set allow_new_privs in new processes (#15229)

patches/common/chromium/.patches.yaml

@@ -55,10 +55,6 @@ patches:
   author: Cheng Zhao <zcbenz@gmail.com>
   file: accelerator.patch
   description: null
--
-  author: Ales Pergl <alpergl@microsoft.com>
-  file: allow_new_privs.patch
-  description: null
 -
   author: null
   file: app_indicator_icon_menu.patch

patches/common/chromium/allow_new_privs.patch

@@ -1,22 +0,0 @@
-From 3a68808c9e49e9a249ee9056015e30543747cd00 Mon Sep 17 00:00:00 2001
-From: Ales Pergl <alpergl@microsoft.com>
-Date: Thu, 20 Sep 2018 17:44:49 -0700
-Subject: allow_new_privs.patch
-
-
-diff --git a/base/process/launch.h b/base/process/launch.h
-index 7a2def2ef436..50afeaf5553a 100644
---- a/base/process/launch.h
-+++ b/base/process/launch.h
-@@ -180,7 +180,7 @@ struct BASE_EXPORT LaunchOptions {
- 
-   // By default, child processes will have the PR_SET_NO_NEW_PRIVS bit set. If
-   // true, then this bit will not be set in the new child process.
--  bool allow_new_privs = false;
-+  bool allow_new_privs = true;
- 
-   // Sets parent process death signal to SIGKILL.
-   bool kill_on_parent_death = false;
--- 
-2.17.0
-