Video Capture Mojo (1.4a.a): Add service configurator interface

services/video_capture/service_manifest.json

Index: services/video_capture/service_manifest.json
diff --git a/services/video_capture/service_manifest.json b/services/video_capture/service_manifest.json
index 1f8aaf92ea2fe7ac98cc9d9c1730c558a893c111..b5cb010c1437927352f864c263a1288469f7cb70 100644
--- a/services/video_capture/service_manifest.json
+++ b/services/video_capture/service_manifest.json
@@ -4,7 +4,8 @@
   "display_name": "Video Capture",
   "capabilities": {
     "provided": {
-      "all": ["*"]
+      "testing": ["*"],
+      "production": ["video_capture::mojom::VideoCaptureDeviceFactory"]

[mcasas, 2016/08/12 23:38:37]

Note that Fake and File VCDevices, despite being
test devices in nature, are shipped in production and
are used out in the wild by dapper developers; 
because of this, I think the distinction testing/production
is unnecessary so, what about just extending the
video_capture_device_factory.mojom's 
VideoCaptureDeviceFactory to have a method
SelectFakeVideoCaptureDevice(FakeDeviceType type)
where the FakeDeviceType would be FILE or FAKE ?
(For more fun, the FileVCD also needs a file path to
operate, but can be read from the command line).

[chfremer, 2016/08/15 20:10:34]

Done.

[chfremer, 2016/08/16 16:48:02]

I removed the differentiation between testing and production for now.

     },
     "required": {
       "mojo:shell": { "classes": [ "shell:all_users" ] }