Suppress MSI/MSM validation when building remoting MSI.

Suppress MSI/MSM validation when building remoting MSI.

I believe this will unblock a required migration in our signing
infrastructure.

BUG=none
R=garykac@chromium.org

Committed: https://crrev.com/819da16a0d1246383bb8fe3c483fe7ace98a60b7
Cr-Commit-Position: refs/heads/master@{#321438}

[Jamie, 2015-03-19 19:31:42]

jamiewalch@chromium.org changed reviewers:
+ jamiewalch@chromium.org

[Jamie, 2015-03-19 19:31:42]

Can you be more specific? What exactly does this validation entail, and why is
it causing problems?

[Jamie, 2015-03-19 21:18:59]

LGTM, but please let us know whether or not this fixes the problem (and revert
if not).

[garykac, 2015-03-19 21:21:19]

The CQ bit was checked by garykac@chromium.org

[commit-bot: I haz the power, 2015-03-19 21:22:46]

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

[commit-bot: I haz the power, 2015-03-19 21:46:14]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-03-19 21:47:08]

Patchset 1 (id:??) landed as
https://crrev.com/819da16a0d1246383bb8fe3c483fe7ace98a60b7
Cr-Commit-Position: refs/heads/master@{#321438}

[grt (UTC plus 2), 2015-03-20 17:53:03]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1028733002/ by grt@chromium.org.

The reason for reverting is: This did the trick. Reverting this change and
putting something durable in the signing infrastructure. Thanks..