Swap to use eleventy-fetch and update to v3

[zachleat]

@11ty/eleventy-cache-assets renamed to @11ty/eleventy-fetch and a new v3.0.0 version.

11ty/eleventy-fetch#18

Full release notes https://github.com/11ty/eleventy-fetch/releases/tag/v3.0.0

Semver note: The problem here is that the cache file algorithm changed, so while this doesn’t technically break backwards compatibility it will require regeneration of new cache files

Note that the algorithm to generate file names used for cache file names changed: previously saved .cache folders generated by eleventy-cache-assets v2 will not be carried forward: new remote requests will be made!

Should this be a new major version? Feels like a minor version thing? Open to feedback here

[zachleat]

Per npm versions info https://www.npmjs.com/package/@11ty/eleventy-img most folks are on 1.0.0

[zachleat]

https://github.com/11ty/eleventy-img/compare/142?expand=1

[zachleat]

Better to be safe than sorry, going with a v2.0.0 here.

[zachleat]

Fixed by ae3ac19