Migrate block 162 to Dart 2.0.

tests/language/language.status

Index: tests/language/language.status
diff --git a/tests/language/language.status b/tests/language/language.status
index c10836d6097dc3f016ad02d5d64740dff17198f9..6eb36c6e7bc8733d9218ec529129a7c6f7769449 100644
--- a/tests/language/language.status
+++ b/tests/language/language.status
@@ -69,7 +69,6 @@ unicode_bom_test: Fail # Issue 16067
 vm/debug_break_enabled_vm_test/01: Crash, OK # Expected to hit breakpoint.
 
 [ ($compiler == none || $compiler == precompiler || $compiler == app_jit) && $checked ]
-type_variable_bounds4_test/01: Fail # Issue 14006

[eernst, 2017/09/04 17:04:58]

In the email thread 'Loss of test coverage' on dart-core-eng started Aug 31st by
ahe@, Bob agreed to change the test migration approach such that the Dart 1.x
tests are _not_ deleted during test migration.

It is probably more work to delete the files and their status entries in this CL
and then later restore them again, so I'd recommend that they are removed from
this CL. That goes for this status line and for other elements, marked below
with "Lost coverage: don't delete".

 
 [ ($compiler == none || $compiler == precompiler || $compiler == app_jit) && ($runtime == vm || $runtime == dart_precompiled || $runtime == flutter) ]
 export_ambiguous_main_negative_test: Fail # Issue 14763
@@ -277,12 +276,6 @@ invocation_mirror_invoke_on_test: CompileTimeError
 method_override3_test/00: CompileTimeError
 method_override3_test/01: CompileTimeError
 method_override3_test/02: CompileTimeError
-type_variable_bounds_test/00: CompileTimeError
-type_variable_bounds_test/06: CompileTimeError
-type_variable_bounds_test/07: CompileTimeError
-type_variable_bounds_test/09: CompileTimeError
-type_variable_bounds_test/10: CompileTimeError
-type_variable_bounds_test/08: CompileTimeError

[eernst, 2017/09/04 17:04:58]

Lost coverage: don't delete lines 280-285.

 factory4_test: CompileTimeError
 factory2_test: CompileTimeError
 regress_18535_test: CompileTimeError