[test] Don't run still-crashing compiler_crashers under no-asserts builds.

Per discussion on the list. From now on, when you fix a compiler_crashers
test case, move it to compiler_crashers_fixed so that we get no-asserts and
ASan coverage.

Swift SVN r27055

validation-test/compiler_crashers_fixed/0189-swift-tuplepattern-create.swift

@@ -0,0 +1,81 @@
+// RUN: not %target-swift-frontend %s -parse
+
+// Distributed under the terms of the MIT license
+// Test case submitted to project by https://github.com/practicalswift (practicalswift)
+// Test case found by fuzzing
+
+class A<T : A> {
+}
+protocol A {
+    typealias E
+}
+struct B<T : As a {
+    typealias b = b
+}
+func a<T>() {f {
+   class func i()
+}
+class d: f{  class func i {}
+func f() {
+    ({})
+}
+func prefix(with: String) -> <T>(() -> T) -> String {
+  return { g in "\(with): \(g  func b(b: X.Type) {
+    }
+}
+class A<T : A> d: f{ func i {}
+col C {
+ : C {
+verride func d() ->  }
+}
+func e<T where T: A, T: B> -> T)!
+    r b
+protocol a : a {
+}
+fu> Bool {
+    return !(a)
+}
+class c {
+    func b((a: (Any, AnyObject)) {
+        b(a)
+    }
+}
+f
+e)
+func f<g>() -> (g, g -> g) -> g {
+   d j d.i = {
+}
+ {
+   g) {
+        h  }
+}
+protocol f {
+   class func i()
+}
+class d: f{  class func i {}
+protocol A {
+    fu]
+}
+func a
+func ^(a: BooleanType, Bool) -> Bool
+ -> Int in
+    return f(x)
+}(x1, f1)
+let crashes: Int = { x, f in
+    return f(x)
+}(x1, f1)
+import Foundation
+class Foo<T>: NS) {
+    return {
+        (m: (Any, Any) -> A in
+        return m(x, y)
+    }
+}
+ 
+func b(z: (((Any, Any) -> Any) -> Any)) -> Any {
+    return z({
+        (p: Any, q:Any) -> Any in
+        return p
+    })
+}
+b(a(1, a(2, 3)))