Drop Incoherent_label_order raise-site comment

It's a live variant with a fixture (labeled_args_incoherent_order.res), so
the behavior is captured by the test, not a comment. Comments are reserved
for removals. The raise site is now identical to master.

Signed-Off-By: Jono Prest <jono@envio.dev>

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: JonoPrest

compiler/ml/typecore.ml

@@ -3874,14 +3874,7 @@ and type_application ~context total_app env funct (sargs : sargs) :
             else if not (has_label l1 ty_fun) then
               raise
                 (Error (sarg1.pexp_loc, env, Apply_wrong_label (l1, ty_res)))
-            else
-              (* Reached when a not-yet-generalized function value is applied
-                 more than once with labelled arguments in conflicting orders
-                 (e.g. `g => (g(~a, ~b), g(~b, ~a))`): the first call fixes the
-                 arrow order, and the second reordered call lands here via the
-                 leftover/tvar path. See
-                 fixtures/labeled_args_incoherent_order.res. *)
-              raise (Error (funct.exp_loc, env, Incoherent_label_order))
+            else raise (Error (funct.exp_loc, env, Incoherent_label_order))
           | _ ->
             raise
               (Error