ci: give the pipeline's imagor the same limits as the suite

CI runs imagor as a service instead of through testcontainers, so the frame limit never reached it and the animation case answered differently there than locally.

.woodpecker.star

@@ -3450,8 +3450,14 @@ def imagorServices():
         "IMAGOR_UNSAFE": True,
         "UPLOAD_LOADER_ENABLE": True,
         "HTTP_LOADER_DISABLE": True,
+        # the limits of the thumbnails service, so both sides refuse the same
+        # requests; keep in step with imagortest.Args, which configures imagor
+        # the same way when the suite starts it through testcontainers
         "VIPS_MAX_WIDTH": 7680,
         "VIPS_MAX_HEIGHT": 7680,
+        "VIPS_MAX_ANIMATION_FRAMES": 100,
+        "UPLOAD_LOADER_MAX_ALLOWED_SIZE": 50000000,
+        "IMAGOR_PROCESS_CONCURRENCY": -1,
     }
 
     return [

services/thumbnails/internal/imagortest/suite.go

@@ -55,6 +55,9 @@ func Variants() []Variant {
 }
 
 // push based processing only: unsigned URLs, uploads in, nothing loaded by URL.
+// CI runs imagor as a pipeline service instead, so .woodpecker.star carries the
+// same values; both have to say the same thing or a parity case answers
+// differently depending on who started the container.
 // Every limit this service has is handed over, so both sides refuse the same
 // requests; imagor's own defaults are looser (a 9999 edge, 32 MB uploads,
 // animations and concurrency unbounded) and would hide a difference as a pass.