gatsby-plugin-image vs gatsby-transformer-sharp for CI builds with bandwidth limits and Sharp dependency concerns

Goal: select image processing plugin that balances build-time efficiency and runtime image optimization under constrained CI bandwidth and potential Sharp installation issues.

Constraints: CI environment may lack necessary vips dependencies, leading to Sharp build failures; limited network bandwidth makes downloading large Sharp binaries costly; need responsive images without excessive build time.

Uncertainty: gatsby-plugin-image offers modern formats and lazy loading but may increase initial build time due to Sharp compilation and caching; gatsby-transformer-sharp may be faster for small image sets but lacks automatic srcset and modern format support without extra plugins.

Which plugin provides the best trade‑off between build time and runtime performance given limited CI bandwidth? How does the need for Sharp system dependencies affect the choice in Alpine‑based CI images? Can gatsby-transformer-sharp be extended to match the responsive features of gatsby-plugin-image without sacrificing build speed?