fix(cache): respect staleMaxAge option

[cjpearson]

🔗 Linked issue

#2164

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This change ensures that stale responses are only used if they have not exceeded the period defined in staleMaxAge.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[TheAlexLichter]

Used it in my project locally and it worked fine 👍🏻

[vercel]

@cjpearson is attempting to deploy a commit to the Nitro Team on Vercel.

A member of the Team first needs to authorize it.

[pi0]

This is now addressed in unjs/ocache (used by Nitro v3):

• staleMaxAge is respected at read time — entries beyond maxAge + staleMaxAge are fully expired and not served stale (cache.ts#L88-L110)
• Stale entries are evicted from storage when background revalidation fails

See unjs/ocache#9