Let jvmti allow JDWP connections

We were incorrectly asserting that the JDWP thread doesn't start until
after the kInit runtime phase has passed but this is not necessarily
the case if JDWP is started with the runtime.

Bug: 35213182
Test: manual
Change-Id: Iea325684fa6a4717176ed8f8070fa1d1bb0e18c7
diff --git a/runtime/openjdkjvmti/ti_thread.cc b/runtime/openjdkjvmti/ti_thread.cc
index b18a5cd..8327b5d 100644
--- a/runtime/openjdkjvmti/ti_thread.cc
+++ b/runtime/openjdkjvmti/ti_thread.cc
@@ -78,7 +78,9 @@
       if (art::kIsDebugBuild) {
         std::string name;
         self->GetThreadName(name);
-        if (name != "Signal Catcher" && !android::base::StartsWith(name, "Jit thread pool")) {
+        if (name != "JDWP" &&
+            name != "Signal Catcher" &&
+            !android::base::StartsWith(name, "Jit thread pool")) {
           LOG(FATAL) << "Unexpected thread before start: " << name;
         }
       }