[win] Create ModuleDatabase and ModuleEventSinkImpl.

chrome/common/conflicts/module_database_win.mojom

Index: chrome/common/conflicts/module_database_win.mojom
diff --git a/chrome/common/conflicts/module_database_win.mojom b/chrome/common/conflicts/module_database_win.mojom
index 2bce402c277630c8a0f0b0634adfe694657df3dd..761fa6635cdac7dee6ef79a4f251a26146dd0f6e 100644
--- a/chrome/common/conflicts/module_database_win.mojom
+++ b/chrome/common/conflicts/module_database_win.mojom
@@ -9,6 +9,10 @@ import "chrome/common/conflicts/module_event_win.mojom";
 
 // Interface for a remote module database.
 interface ModuleDatabase {
+  // Notifies the module database of a remote process that has just started,
+  // including its |process_id| and |process_type|. The |process_type| is from
+  // the enumeration in "content/public/common/process_type.h".
+  OnProcessStarted(uint32 process_id, uint32 process_type);

[grt (UTC plus 2), 2016/12/15 09:07:12]

does |process_id| come across the wire from the child proc? if yes, why? does
the browser not know its children's pids?

[chrisha, 2016/12/19 20:15:37]

Yup, this was silly. Reworked this so that it's taken directly from the process
handle in the browser process.

   // Notifies the module database of a module event in a remote process.
-  OnModuleEvent(uint32 process_id, ModuleEvent module_event);
+  OnModuleEvent(ModuleEvent module_event);

[chrisha, 2016/12/19 20:15:37]

After talking to security folks (wfh@), also reworked this so that only the load
address is transmitted (which is verifiable in the browser process). All of the
other information can then be queried directly from the OS in the browser
process, without having to trust any data from the child process.

 };