Supply an explicit designated requirement for all internal components during signing

Supply an explicit designated requirement for all internal components during
signing.

The implied designated requirement produced when signing on Lion cannot be
satisfied on pre-Lion systems. This was already addressed by providing an
explicit designated requirement for the outer .app bundle. This change also
provides an explicit designated requirement for inner components.

The Parental Controls feature apparently requires an application to meet its
designated requirement. Since the requirement for inner components such as
the helper would never be met on 10.6 (or presumably 10.5), it was impossible
to launch such inner components. This prevented any renderer processes from
ever starting up. The user would only see sad tabs and endless OS prompts, and
the browser would effectively be useless.

BUG=131682, 134311
TEST=Turn on Parental Controls and set it to limit applications. Launch Chrome.
     After a possible initial prompt asking whether Chrome should be permitted
     (authenticate and say yes), Chrome should function normally. There should
     be no prompts about Chrome Helper, Chrome Helper EH, or Chrome Helper NP.
     Web pages should load normally. There should be no sad tabs. Note that
     there may still be a prompt about ksadmin.
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=145370

[Mark Mentovai, 2012-07-03 19:19:37]

Tom’s out for a while, so I’ll send this to Nico for now.

[Nico, 2012-07-03 19:41:26]

I'm out too (at sfo atm)
On Jul 3, 2012 12:19 PM, <mark@chromium.org> wrote:

> Tom’s out for a while, so I’ll send this to Nico for now.
>
>
https://chromiumcodereview.**appspot.com/10696101/<https://chromiumcodereview...
>

[Mark Mentovai, 2012-07-03 19:42:11]

Have a nice trip.

Robert, then.

[Robert Sesek, 2012-07-03 20:34:56]

LG™