Java: Move diagnostic_for next to diagnostics in the dbscheme

No code change, but it makes a bit more sense there

Author: igfoo

java/ql/lib/config/semmlecode.dbscheme

@@ -138,21 +138,6 @@ compilation_time(
     float seconds : float ref
 );
 
-/**
- * An error or warning generated by the extractor.
- * The diagnostic message `diagnostic` was generated during compiler
- * invocation `compilation`, and is the `file_number_diagnostic_number`th
- * message generated while extracting the `file_number`th file of that
- * invocation.
- */
-#keyset[compilation, file_number, file_number_diagnostic_number]
-diagnostic_for(
-    unique int diagnostic : @diagnostic ref,
-    int compilation : @compilation ref,
-    int file_number : int ref,
-    int file_number_diagnostic_number : int ref
-);
-
 /**
  * The `cpu_seconds` and `elapsed_seconds` are the CPU time and elapsed
  * time (respectively) that the original compilation (not the extraction)
@@ -191,6 +176,21 @@ diagnostics(
     int location: @location_default ref
 );
 
+/**
+ * An error or warning generated by the extractor.
+ * The diagnostic message `diagnostic` was generated during compiler
+ * invocation `compilation`, and is the `file_number_diagnostic_number`th
+ * message generated while extracting the `file_number`th file of that
+ * invocation.
+ */
+#keyset[compilation, file_number, file_number_diagnostic_number]
+diagnostic_for(
+    unique int diagnostic : @diagnostic ref,
+    int compilation : @compilation ref,
+    int file_number : int ref,
+    int file_number_diagnostic_number : int ref
+);
+
 /*
  * External artifacts
  */