test: Replace _TEST_CASE_ with _TEST_SUITE_ in /chrome/browser/ui/extensions.

Googletest is (at last) converging with industry-standard terminology
[1]. We previously called test suites "test cases", which was rather
confusing for folks coming from any other testing framework.

Chrome now has a googltest version that supports _TEST_SUITE_ macros
instead of _TEST_CASE_, so this CL cleans up some of the outdated usage.

[1] https://github.com/google/googletest/blob/master/googletest/docs/primer.md#beware-of-the-nomenclature

This CL was uploaded by git cl split.

R=benwells@chromium.org

Bug: 925652
Change-Id: Ibebae3e41aeb0549156b1aace0aa7197e821fe62
Reviewed-on: https://chromium-review.googlesource.com/c/1438317
Commit-Queue: Ben Wells <benwells@chromium.org>
Reviewed-by: Ben Wells <benwells@chromium.org>
Cr-Commit-Position: refs/heads/master@{#626924}

chrome/browser/ui/extensions/extension_action_view_controller_unittest.cc

@@ -407,9 +407,9 @@ TEST_P(ExtensionActionViewControllerGrayscaleTest,
   RunGrayscaleTest(PermissionType::kScriptableHost);
 }
 
-INSTANTIATE_TEST_CASE_P(,
-                        ExtensionActionViewControllerGrayscaleTest,
-                        testing::Values(false, true));
+INSTANTIATE_TEST_SUITE_P(,
+                         ExtensionActionViewControllerGrayscaleTest,
+                         testing::Values(false, true));
 
 TEST_P(ToolbarActionsBarUnitTest, RuntimeHostsTooltip) {
   base::test::ScopedFeatureList feature_list;