feat!: add preload and prefetch attributes to manifest

[danielroe]

resolves #45

This adds backwards-compatible build-time analysis on whether to prefetch/preload resources. It should be exactly compatible with current default runtime values as moves the runtime code to build-time (and defers to any custom shouldPrefetch/shouldPreload that is passed).

Refactored to be a breaking change.

[codecov-commenter]

Codecov Report

Merging #50 (ce3b75a) into main (ad2e20e) will increase coverage by 0.00%.
The diff coverage is 100.00%.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@           Coverage Diff           @@
##             main      #50   +/-   ##
=======================================
  Coverage   97.54%   97.55%           
=======================================
  Files           6        6           
  Lines         530      532    +2     
  Branches      112      112           
=======================================
+ Hits          517      519    +2     
  Misses         13       13           

Files Changed	Coverage Δ
src/runtime.ts	99.27% <100.00%> (-0.03%)	⬇️
src/types.ts	92.59% <100.00%> (+0.59%)	⬆️
src/utils.ts	100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[danielroe]

We could alternatively entirely remove the shouldPreload/shouldPrefetch and make a major version bump.

[pi0]

I love it! I think making a mjaor version + removing runtime hooks makes sense because if someone uses resolution in runtime and does not have build-time flags (with new build), it won't work.

[danielroe]

Let's go for major version then. Though I do think this (as-is) is backwards compatible. (We require manifests to be normalised, not just for this reason.)