Make NOTIFICATION_HISTORY_URLS_MODIFIED fired consistently for both typed and non-typed URLs

Make NOTIFICATION_HISTORY_URLS_MODIFIED fired consistently for both typed and non-typed URLs.

The semantics for NOTIFICATION_HISTORY_URLS_MODIFIED was changed as of revision 131865 (https://chromiumcodereview.appspot.com/9852002) so that it would be fired not only for typed URLs, but also for non-typed ones (that is, URLs having |typed_count| == 0).

However, HistoryBackend::AddPagesWithDetails() was not updated to reflect these new semantics. Rectify this omission to make the code less mysterious.

BUG=None

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

[engedy, 2014-06-10 17:56:20]

@Brett: Please take a look.

The new implementation is in line with the existing semantics of the
notification. Furthermore, I believe the change in behavior will not cause any
problems for the existing 3 observers either, because:
 1.) InMemoryHistoryBackend: I have recently refactored this myself to do the
filtering on its own.
 2.) TypedUrlChangeProcessor: This had been explicitly filtering out non-typed
URLs already.
 3.) InMemoryURLIndex: This does not seem to care about |typed_count|, but is
feeded non-typed URLs through other channels already, and this seems to be the
right thing to do anyway, because I believe want to offer Omnibox
auto-completion of titles of visited (but not typed) URLs.

[brettw, 2014-06-11 21:58:41]

lgtm

[engedy, 2014-06-11 22:01:57]

The CQ bit was checked by engedy@chromium.org

[commit-bot: I haz the power, 2014-06-11 22:04:50]

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

[commit-bot: I haz the power, 2014-06-12 00:52:49]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  ios_dbg_simulator on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_dbg_simulator/bui...)
  ios_rel_device on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device/builds...)
  ios_rel_device_ninja on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device_ninja/...)
  mac_chromium_compile_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_compile_...)
  win_chromium_compile_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_compile_...)
  win_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)
  win_chromium_x64_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_x64_rel/...)
  mac_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu/builds/15803)
  win_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/win_gpu/builds/18938)

[commit-bot: I haz the power, 2014-06-12 00:54:33]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-06-12 00:54:35]

Try jobs failed on following builders:
  mac_chromium_compile_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_compile_...)
  win_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)
  win_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/win_gpu/builds/18963)

[engedy, 2014-06-12 07:27:24]

The CQ bit was checked by engedy@chromium.org

[commit-bot: I haz the power, 2014-06-12 07:31:51]

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

[commit-bot: I haz the power, 2014-06-12 11:02:45]

Change committed as 276622