[iOS Clean] Wired up ContextMenuCommands.

ios/clean/chrome/browser/ui/context_menu/context_menu_mediator.h

Index: ios/clean/chrome/browser/ui/context_menu/context_menu_mediator.h
diff --git a/ios/clean/chrome/browser/ui/context_menu/context_menu_mediator.h b/ios/clean/chrome/browser/ui/context_menu/context_menu_mediator.h
index 3639b336280a1d5f1126c18b27e4c569dafa7ef3..6180d694b574d221a742a542a1a56b5775448785 100644
--- a/ios/clean/chrome/browser/ui/context_menu/context_menu_mediator.h
+++ b/ios/clean/chrome/browser/ui/context_menu/context_menu_mediator.h
@@ -8,13 +8,18 @@
 #import <Foundation/Foundation.h>
 
 @protocol ContextMenuConsumer;
+@class ContextMenuContextImpl;
 
 // A mediator object that provides configuration information for a context
 // menu.
 @interface ContextMenuMediator : NSObject

[edchin, 2017/05/25 21:41:53]

Note: this is the only mediator that I know of that isn't an observer
of some asynchronous events. This mediator simply processes 
some input and calls methods on the consumer in the initializer. 
So it's a bit different. But I'm not making an argument to change
anything here.

[kkhorimoto, 2017/05/26 23:20:09]

The mediator's main purpose is to act as the middle man between the coordinator
layer and the view layer, so populating the UI it's presenting is accomplishing
that.  I think it's a little different because everything that's needed for this
UI is already available when creating the coordinator and it never changes (so
there's no need for observers or other updates).

 
-// Creates a new mediator with the non-nil consumer |consumer|.
-- (instancetype)initWithConsumer:(id<ContextMenuConsumer>)consumer;
+// Creates a new mediator with the non-nil consumer |consumer|.  |context| is
+// used to supply the consumer with its title and ContextMenuItems.
+- (instancetype)initWithConsumer:(id<ContextMenuConsumer>)consumer
+                         context:(ContextMenuContextImpl*)context
+    NS_DESIGNATED_INITIALIZER;
+- (instancetype)init NS_UNAVAILABLE;
 
 @end