[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/1660-swift-parser-parseexprsequence.swift

@@ -0,0 +1,43 @@
+// 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
+
+// Distributed under the terms of the MIT license
+// Test case submitted to project by https://github.com/practicalswift (practicalswift)
+// Test case found by fuzzing
+
+func a<d.c: Int>() -> V {
+struct c: C = Int
+typealias e == A> String {
+}
+return [1, A {
+let foo as String)) {
+func f<d {
+}
+enum A {
+convenience init<1 {
+public var _ c(() {
+class a {
+func b() -> () -> Any) -> {
+}
+}
+protocol A {
+}
+for () -> : Hashable> Void>(Any) -> Any] {
+let a(T> S) {
+}
+func f: AnyObject) -> (A, self.Generator.Element == g<U)) {
+}
+}() -> T>()
+return x {
+}
+}
+}
+}
+}
+}
+typealias h>([unowned self, A {
+var f == "
+for c {