fix(webapp): no compensation on the not-overridden validation error

Resetting a limit with no override fails before any engine write, so
the compensating re-sync is skipped for that error instead of issuing
spurious reads and engine writes on a pure validation path.

Author: matt-aitken

apps/webapp/app/v3/services/concurrencyLimitsSystem.server.ts

@@ -136,9 +136,11 @@ export class ConcurrencyLimitsSystem {
         return findLimitByName(this.db, environment, name)
           .andThen((row) =>
             syncResetToEngine(environment, row).orElse((error) =>
-              compensateEngineFromFreshRow(this.db, environment, row.id)
-                .orElse(() => okAsync(undefined))
-                .andThen(() => errAsync(error))
+              error.type === "limit_not_overridden"
+                ? errAsync(error)
+                : compensateEngineFromFreshRow(this.db, environment, row.id)
+                    .orElse(() => okAsync(undefined))
+                    .andThen(() => errAsync(error))
             )
           )
           .andThen((row) =>