Revert of Expose camera settings to the extensions.

Revert of Expose camera settings to the extensions. (patchset #3 id:80001 of https://codereview.chromium.org/889893002/)

Reason for revert:
Setting the camera and microphone default content settings currently cannot be shown in the UI and will not work exactly the way an app developer might expect it to (due to interference with the MEDIASTREAM content setting).

Reverting this patch until the UI is ready.


Original issue's description:
> Expose camera settings to the extensions.
> 
> BUG=453773
> DIFFBASE=880223002
> 
> Committed: https://crrev.com/2b3079c96f41b136c66d787b3bfa39ee17084cd4
> Cr-Commit-Position: refs/heads/master@{#314319}

TBR=mkwst@chromium.org,kalman@chromium.org
BUG=453773

[msramek, 2015-02-18 11:24:54]

Created Revert of Expose camera settings to the extensions.

[commit-bot: I haz the power, 2015-02-18 11:25:26]

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

[commit-bot: I haz the power, 2015-02-18 11:25:27]

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

[commit-bot: I haz the power, 2015-02-18 11:25:28]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[Mike West, 2015-02-18 11:42:47]

LGTM.

It's been long enough that notry/nopresubmit is probably a bad idea. Please let
this run through the CQ as usual.

[msramek, 2015-02-18 11:44:57]

The CQ bit was checked by msramek@chromium.org

[commit-bot: I haz the power, 2015-02-18 11:45:27]

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

[commit-bot: I haz the power, 2015-02-18 11:47:58]

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

[commit-bot: I haz the power, 2015-02-18 11:47:59]

Try jobs failed on following builders:
  ios_dbg_simulator on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_dbg_simulator...)
  ios_rel_device_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device_ng...)
  ios_rel_device_ninja_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device_ni...)
  mac_chromium_compile_dbg_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
  mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[msramek, 2015-02-18 11:52:27]

On 2015/02/18 11:42:47, Mike West wrote:
> LGTM.
> 
> It's been long enough that notry/nopresubmit is probably a bad idea. Please
let
> this run through the CQ as usual.

Good point. And trybots have indeed failed. Automatic revert is impossible here,
as we cannot remove the options from test.js and content_settings_helpers.cc.