[Hotword] Update the version number of the component extension.

[Hotword] Update the version number of the component extension.

Due to not updating the version number, the list of events 
listened for by the component extension was not being 
updated. Therefore, profiles who had been using hotwording
for a while now were still listening for events on tab 
events and therefore opening the hotword helper on any 
all tab events.

By updating the version number, it will overwrite the events 
list and the helper should now only wake up upon messages 
directed to it from our specified locations.

I've jumped from 1 to 2 because in reality, that's about 
where we should be based on the number of changes since 
version 1.0.

BUG=400579, 378844
TEST=
1) Run chrome with an old version such as 36.
2) In the Preferences file (<profile name>/Preferences) in the section named "dnhpdliibojhegemfjheidglijccjfmc", there should be a list named "events" which should look like: "events": [ "hotwordPrivate.onEnabledChanged", "tabs.onActivated", "tabs.onUpdated" ],
3) Now run the new version in the same profile directory.
4) In the same file and section as step 2, the "events" list should look like: "events": [ ]

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=288939

[James Hawkins, 2014-08-11 14:12:54]

lgtm

[rpetterson, 2014-08-11 17:03:35]

The CQ bit was checked by rlp@chromium.org

[commit-bot: I haz the power, 2014-08-11 17:05:17]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/rlp@chromium.org/457863002/1

[commit-bot: I haz the power, 2014-08-11 20:47:05]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_chromium_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel/...)

[commit-bot: I haz the power, 2014-08-12 11:56:15]

Change committed as 288939