[⚡ Feature]: Implement next-suspense-cache header

[WalshyDev]

Description

The suspense cache is currently a bit of a black box, customers don't know it's happening and cannot see if users are being served cached content.

I'd like for us to add a next-suspense-cache header which will have HIT/MISS/DYNAMIC (? e.g. disabled) so customers can know quickly and easily.

This diverges slightly from Next however, given the current black box behaviour and the fact customers keep running up against it I think it's more than fair to do this.

Additional Information

No response

Would you like to help?

• Would you like to help implement this feature?