Add menu option for disabling app notifications

chrome/app/generated_resources.grd

Index: chrome/app/generated_resources.grd
diff --git a/chrome/app/generated_resources.grd b/chrome/app/generated_resources.grd
index 1da01df0a6045a5b355419a79967392bac074146..f49146b6ba0bde5646d61bdd7b931e5dfb15d7b8 100644
--- a/chrome/app/generated_resources.grd
+++ b/chrome/app/generated_resources.grd
@@ -8953,6 +8953,9 @@ experiment id: "<ph name="EXPERIMENT_ID">$5<ex>ar1</ex></ph>"
                desc="Text for the button that takes the user to the options of an app.">
         Options
       </message>
+      <message name="IDS_NEW_TAB_APP_DISABLE_NOTIFICATIONS" desc="Text for the option to disable app notifications">
+        Disable notifications

[Evan Stade, 2011/12/05 23:19:32]

sorry I didn't think of this prior, but it seems better to keep action strings
positive, i.e. this could be "Allow notifications" and its meaning inverted of
course. Perhaps best to get a UI lead to weigh in.

[asargent_no_longer_on_chrome, 2011/12/06 00:14:55]

Actually just a little while ago today Glen chimed in on a thread suggesting the
same thing, with the verb of either "Enable" or "Allow". I need to pin down
which of the two we want, but would like to proceed with this CL for now. (BTW,
this entire feature is going to be gated with a webstore service with just
trusted testers for a while - the messages that show up get sent to this service
and delivered through the sync channel. So we just want to get the functionality
into the client for M17 so we can dogfood a while and make incremental
improvements based on dogfooding).

I have a separate CL getting the strings in for the translation cutoff
(http://codereview.chromium.org/8801032/), so we can do a patch to switch if we
want.

+      </message>
       <message name="IDS_NEW_TAB_APP_CREATE_SHORTCUT"
                desc="Text for the button that creates an app shortcut.">
         Create shortcut