In preparation for adding appcontainer token to renderer, these are content side changes.

In preparation for adding appcontainer token to renderer, these are content side changes.
In this CL, we add appcontainer related attributes in PreSpawnTarget for renderer. Though we modify policy here, it is still not being honored, that will happen in next CL.

BUG=455496
R=cpu, jschuh, rvargas

Committed: https://crrev.com/7e41fb89274cd1f3e71d3bd6e5b75e211b8fa103
Cr-Commit-Position: refs/heads/master@{#319208}

[Shrikant Kelkar, 2015-02-23 21:43:19]

ptal.

[Shrikant Kelkar, 2015-02-24 20:36:30]

shrikant@chromium.org changed reviewers:
+ rvargas@chromium.org

[Shrikant Kelkar, 2015-02-24 20:37:05]

+rvargas
separated content related code. ptal.

[Shrikant Kelkar, 2015-02-25 00:15:34]

ptal.
After discussion with rvargas@ removed sid changes and for now added static
appcontainer sid.

[Shrikant Kelkar, 2015-03-02 21:25:15]

ptal.
These are content side changes after landing sandbox side changes.

[cpu_(ooo_6.6-7.5), 2015-03-02 22:31:33]

lgtm

https://codereview.chromium.org/949943003/diff/80001/content/browser/renderer...
File content/browser/renderer_host/render_process_host_impl.cc (right):

https://codereview.chromium.org/949943003/diff/80001/content/browser/renderer...
content/browser/renderer_host/render_process_host_impl.cc:341: 
at least lets have two sids, one for chrome and one for chromium.

[Shrikant Kelkar, 2015-03-02 23:03:44]

https://codereview.chromium.org/949943003/diff/80001/content/browser/renderer...
File content/browser/renderer_host/render_process_host_impl.cc (right):

https://codereview.chromium.org/949943003/diff/80001/content/browser/renderer...
content/browser/renderer_host/render_process_host_impl.cc:341: 
On 2015/03/02 22:31:32, cpu wrote:
> at least lets have two sids, one for chrome and one for chromium.

Okay, then actually should I add policy inside 
content/shell/browser/shell_content_browser_client.cc and
chrome/browser/chrome_content_browser_client.cc PreSpawnTarget().

This way whichever clients want to put in appcontainer will be able to do so.

[Shrikant Kelkar, 2015-03-02 23:03:56]

The CQ bit was checked by shrikant@chromium.org

[commit-bot: I haz the power, 2015-03-02 23:04:21]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/949943003/80001

[commit-bot: I haz the power, 2015-03-03 03:43:08]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-03-03 03:43:09]

Try jobs failed on following builders:
  win8_chromium_rel on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win8_chromium_rel...)

[Shrikant Kelkar, 2015-03-05 02:12:50]

The CQ bit was checked by shrikant@chromium.org

[commit-bot: I haz the power, 2015-03-05 02:14:51]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/949943003/80001

[commit-bot: I haz the power, 2015-03-05 03:49:51]

Committed patchset #5 (id:80001)

[commit-bot: I haz the power, 2015-03-05 03:50:38]

Patchset 5 (id:??) landed as
https://crrev.com/7e41fb89274cd1f3e71d3bd6e5b75e211b8fa103
Cr-Commit-Position: refs/heads/master@{#319208}