next.js

df4bb11d - Mark revalidate: 0 on fetch or use cache as never resolving promise in Dynamic I/O (#71285)

Mark revalidate: 0 on fetch or use cache as never resolving promise in Dynamic I/O (#71285) This marks it as dynamic but not "sync abort" since these are not sync APIs. A new heuristic here is that if the `expire` time is low, then we also treat that as dynamic for the purpose of prerendering since it's not worth including if it's supposed to change frequently but it is still possible to temporarily cache it or client-cache it.