Import keywords for search engines imported from Firefox

chrome/test/data/firefox_profile/search.json

Index: chrome/test/data/firefox_profile/search.json
diff --git a/chrome/test/data/firefox_profile/search.json b/chrome/test/data/firefox_profile/search.json
index cae0cb946801e1e7193e98e8cad38ef067d6a0f5..16084d3b5414b6d79375be80ef018b2a61ba3de9 100644
--- a/chrome/test/data/firefox_profile/search.json
+++ b/chrome/test/data/firefox_profile/search.json
@@ -72,6 +72,16 @@
         "filePath":"[app]/yahoo.xml",
         "_installLocation":3,
         "queryCharset":"UTF-8"
+      },
+      {
+        "_id":"./chrome/test/data/firefox_searchplugins/default/twitter.xml",

[Peter Kasting, 2014/07/31 18:28:21]

Any particular reason to add this?  I'm not seeing a way that it differs from
the entries above and thus would lead to greater test coverage.  Why can't you
just add an alias in search-metadata.json for one of the existing entries,
instead of adding this new one so you can add to it?

[Nikhil, 2014/08/04 12:15:11]

I added new entry in .json files since tests for older versions of Firefox
compared against keywords set in kFirefoxKeywords. I couldn't get all tests to
pass if I changed an existing entry.

But I've now slightly changed the approach based on your suggestion. PTAL.

+        "_name":"Twitter",
+        "_hidden":false,
+        "description":"Realtime Twitter Search",
+        "_searchForm":"https://twitter.com/search/",
+        "filePath":"[app]/twitter.xml",
+        "_installLocation":3,
+        "queryCharset":"UTF-8"
       }]
     },
     "/home/tapughose/.mozilla/firefox/lcd50n4n.default/searchplugins":