cache-control headers being overwritten by routes

[Frederik Nordahl]

As per this issue in the forums: https://community.frontity.org/t/vercel-raise-issue-frontity-heading-cache-network-isssue/5580

I'm also experiencing issues with cache control headers being set by the router: https://github.com/frontity/now-builder/blob/master/src/index.ts#L123-L127 meaning I can't make use of vercel's excellent edge network cdn :(

A fix would be not setting cache control at all perhaps, and just let the vercel.json decide :)

Br,
Frederik