[test] Mark tests that use experimental/upcoming features as such

Find all the usages of `--enable-experimental-feature` or
`--enable-upcoming-feature` in the tests and replace some of the
`REQUIRES: asserts` to use `REQUIRES: swift-feature-Foo` instead, which
should correctly apply to depending on the asserts/noasserts mode of the
toolchain for each feature.

Remove some comments that talked about enabling asserts since they don't
apply anymore (but I might had miss some).

All this was done with an automated script, so some formatting weirdness
might happen, but I hope I fixed most of those.

There might be some tests that were `REQUIRES: asserts` that might run
in `noasserts` toolchains now. This will normally be because their
feature went from experimental to upcoming/base and the tests were not
updated.

test/Interpreter/lazy/deferred_syntax_errors.swift

@@ -2,9 +2,8 @@
 // REQUIRES: swift_interpreter
 // RUN: %target-jit-run %s -enable-experimental-feature LazyImmediate | %FileCheck %s
 
-// -enable-experimental-feature requires an asserts build
-// REQUIRES: asserts
 // REQUIRES: rdar118189728
+// REQUIRES: swift_feature_LazyImmediate
 
 // Tests that parsing of function bodies is deferred
 // to runtime when the interpreter is invoked using