Migrated cascades tests from dart2js_extra into language tests

tests/language/language.status

Index: tests/language/language.status
diff --git a/tests/language/language.status b/tests/language/language.status
index f4a9a2ee899521d1cf4713da81dc200978837f95..ca100b4881e1161ccf7c49c5705963fa6d9bd761 100644
--- a/tests/language/language.status
+++ b/tests/language/language.status
@@ -52,6 +52,10 @@ parameter_initializer6_negative_test: Fail # Issue 3502
 
 prefix_core_test: Fail # Issue 3638.
 
+# Issue 2501
+cascade_test: Pass,Fail  # Some cases pass, but for the wrong reason  

[kasperl, 2012/06/19 13:47:15]

You could also split them out into the different /01 variants, but I guess this
is easier for now -- and still allows you to start making progress.

[zundel, 2012/06/19 13:54:31]

Enumerating them out isn't any more helpful IMHO.  The feature is unimplemented.
The tests that 'pass' do so because a compile time error is expected but really
its a syntax error on not being able to parse the cascade syntax.

+cascade_precedence_test: Fail 
+
 # DartC or Frog specific tests that should not be run by the VM
 *dartc_test: Skip
 *dartc_negative_test: Skip
@@ -67,6 +71,8 @@ assert_keyword_negative_test: Fail # Runtime only test, rewrite as multitest
 assign_instance_method_negative_test: Fail  # Issue 3662
 body_less_constructor_wrong_arg_negative_test: Fail  # Runtime only test, rewrite as multitest
 call_operator_test: Pass # Issue 1355  
+cascade_test: Pass,Fail # Issue 3729  Some cases pass, but for the wrong reason
+cascade_precedence_test: Fail  # Issue 3729
 char_escape_test: Pass # Issue 1654
 closure_call_wrong_argument_count_negative_test: Fail # Runtime only test, rewrite as multitest
 compile_time_constant_p_test/01: Fail # Issue 2580