[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/0895-swift-tuplepattern-create.swift

@@ -0,0 +1,36 @@
+// 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
+
+func f<o>() -> (o, o -> o) -> o {
+o m o.j = {
+}
+{
+o) {
+r  }
+}
+p q) {
+}
+o m  {
+f r f.j = {
+}
+{
+r) {
+s  }
+}
+protocol f {
+}
+class f: f{  class func j {}
+protocol j {
+}
+class r: j {
+}
+protocol r {
+class func q()
+}
+}
+}
+class e: f {
+class f.G