Whoops, fix outfitImage caching bug

I was accidentally serving images _without_ `updatedAt` with the long-term cache headers, but only in prod, not in dev

I think this is probably because I made a mistake in my Vercel route config, by including an `$updatedAt` parameter that doesn't actually exist in this case.

I'm guessing the Vercel dev server has different behavior for my mistake than the prod server. I'm guessing the dev server makes it an empty string, and the prod server makes it the literal string `$updatedAt`. Oops!

I hope this fixes it!

vercel.json

@@ -2,7 +2,7 @@
   "routes": [
     {
       "src": "/outfits/(?<id>[^/]+)/(?<size>150|300|600).png",
-      "dest": "/api/outfitImage.js?size=$size&id=$id&updatedAt=$updatedAt"
+      "dest": "/api/outfitImage.js?size=$size&id=$id"
     },
     {
       "src": "/outfits/(?<id>[^/]+)/v/(?<updatedAt>[^/]+)/(?<size>150|300|600).png",