feat: upload dev tools images to s3 on trigger task

[wackerow]

Summary

• Upload developer tool images (thumbnails and banners) to S3 during the trigger.dev fetch task
• Follows the same pattern already used by fetchEvents for event images
• Prevents hotlinking external image sources by re-hosting on our S3 bucket

Test plan

• Ran fetch-developer-tools trigger task locally -- all 226 tools processed
• Confirmed S3 uploads for both tools/thumbnails/ and tools/banners/ prefixes
• Verified deduplication works on re-run (only previously failed uploads were retried)

Todo

• Make sure next.config changes from feat: new /developer/tools pages #17110 are no longer needed then remove the following:

        { protocol: "https", hostname: "storage.googleapis.com" },
        { protocol: "https", hostname: "cdn.charmverse.io" },
        { protocol: "https", hostname: "ethwingman.com" },
        { protocol: "https", hostname: "eth-mcp.dev" },

(Non-blocking todo)

[netlify]

✅ Deploy Preview for ethereumorg ready!

Name	Link
🔨 Latest commit	881c772
🔍 Latest deploy log	https://app.netlify.com/projects/ethereumorg/deploys/69aa21cf0c0b8300089dd75f
😎 Deploy Preview	https://deploy-preview-17723.ethereum.it
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	7 paths audited Performance: 59 (🔴 down 1 from production) Accessibility: 94 (🟢 up 1 from production) Best Practices: 100 (no change from production) SEO: 99 (no change from production) PWA: 59 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.