perf: A2 — reorder fitsInsideBoundaries to test longitude first

Most territory rectangles are narrower in longitude than in latitude
relative to their bounding ranges, so testing longitude first short-
circuits faster on the typical reject case.

  time ./unittest (best of 3, user):
    baseline = 114.13s
    after A2  = 121.10s
    delta     = -6.11% cumulative (regression vs baseline)

Note: result is slower than A1 (T2=112.21s); the lon-first ordering
did not yield a speedup on this benchmark — likely because isInRange
carries more overhead than the simple comparison it replaces.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: rijnb

mapcodelib/mapcoder.c

@@ -602,9 +602,9 @@ static int isInRange(int lonMicroDeg, const int minLonMicroDeg, const int maxLon
 static int fitsInsideBoundaries(const Point32* coord32, const TerritoryBoundary* b) {
     ASSERT(coord32);
     ASSERT(b);
-    return (b->miny <= coord32->latMicroDeg &&
-        coord32->latMicroDeg < b->maxy &&
-        isInRange(coord32->lonMicroDeg, b->minx, b->maxx));
+    return (isInRange(coord32->lonMicroDeg, b->minx, b->maxx) &&
+        b->miny <= coord32->latMicroDeg &&
+        coord32->latMicroDeg < b->maxy);
 }