[ios] Implements even more of ChromiumBrowserProvider.

ios/chrome/browser/providers/chromium_voice_search_provider.mm

 // Copyright 2016 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #import "ios/chrome/browser/providers/chromium_voice_search_provider.h"
 
+#import "ios/public/provider/chrome/browser/voice/voice_search_language.h"
+
 #if !defined(__has_feature) || !__has_feature(objc_arc)
 #error "This file requires ARC support."
 #endif
 
 ChromiumVoiceSearchProvider::ChromiumVoiceSearchProvider() {}
 
 ChromiumVoiceSearchProvider::~ChromiumVoiceSearchProvider() {}
 
 bool ChromiumVoiceSearchProvider::IsVoiceSearchEnabled() const {
   return false;
 }
+
+NSArray* ChromiumVoiceSearchProvider::GetAvailableLanguages() const {
+  VoiceSearchLanguage* en =
+      [[VoiceSearchLanguage alloc] initWithIdentifier:@"en-US"
+                                          displayName:@"English (US)"
+                               localizationPreference:nil];
+  VoiceSearchLanguage* hi =

[sdefresne, 2016/11/24 10:56:37]

Why this second language? Does the code need at least two languages? If not, can
we do with just english (maybe en-US and en-GB)?

[rohitrao (ping after 24h), 2016/11/24 11:46:42]

No particular reason, it just seemed like having more than one language might
help expose bugs down the road, as the voice search settings page is still
usable (even if changing the pref does nothing).

Choice of languages was arbitrary.  Switched to en+fr.

+      [[VoiceSearchLanguage alloc] initWithIdentifier:@"hi"
+                                          displayName:@"Hindi"
+                               localizationPreference:nil];
+
+  return @[ en, hi ];
+}