Update avatar button to MD (part 1)

chrome/browser/ui/views/profiles/avatar_button_delegate.h

Index: chrome/browser/ui/views/profiles/avatar_button_delegate.h
diff --git a/chrome/browser/ui/views/profiles/avatar_button_delegate.h b/chrome/browser/ui/views/profiles/avatar_button_delegate.h
index a5f0bb60559bc443a36e635632e5e99e527884d1..f8f6a440f873a90c8262b541db65def82df2705b 100644
--- a/chrome/browser/ui/views/profiles/avatar_button_delegate.h
+++ b/chrome/browser/ui/views/profiles/avatar_button_delegate.h
@@ -5,10 +5,10 @@
 #ifndef CHROME_BROWSER_UI_VIEWS_PROFILES_AVATAR_BUTTON_DELEGATE_H_
 #define CHROME_BROWSER_UI_VIEWS_PROFILES_AVATAR_BUTTON_DELEGATE_H_
 
-#include "ui/views/controls/button/button.h"
+#include "ui/views/controls/button/menu_button_listener.h"
 
 // Delegate allowing NewAvatarButton to communicate back to its manager.
-class AvatarButtonDelegate : public views::ButtonListener {
+class AvatarButtonDelegate : public views::MenuButtonListener {
  public:
   // Called when the preferred size changed, e.g., due to a profile name change.
   virtual void ButtonPreferredSizeChanged() = 0;

[Evan Stade, 2017/04/27 17:15:02]

this is not your doing, but it seems like we shouldn't need this but could
instead use View::PreferredSizeChanged() and
View::ChildPreferredSizeChanged(View* child). The appropriate view that holds
the button can check if the child matches the avatar button and act accordingly.
This would eliminate this class and simplify AvatarButtonManager, and delete
this code which seems out of place in that class:

  frame_view_->InvalidateLayout();
  frame_view_->frame()->GetRootView()->Layout();

[emx, 2017/04/28 12:39:40]

Thanks, this simplifies things quite a bit!