Warn/Error if next is run without cacheComponents: true if the site was built with cacheComponents: true

[webmonarch]

Goals

1. Avoid the "footgun" of: build with cacheComponents: true, deploy somehow and either (1) forgetting to include the proper configuration (or the configuration was not read for some reason (without TS)
2. When this happens, consider updating the documentation to suggest this could be the cause for "DYNAMIC_SERVER_USAGE" error
3. Consider a more suggestive error message than: "Page changed from static to dynamic at runtime %s%s\nsee more here https://nextjs.org/docs/messages/app-static-to-dynamic-error"

Non-Goals

1. Changing the behavior of caching in any way, just error / warning messaging

Background

I spent a while debugging this issue where cacheComponents: true dynamic pages would error when deployed on any call to a dynamic function (eg: await connection()). It took my a while to realize that my deploy process forgot to include the next.config file. (somewhat related, it deployed a production version of the app (no dev depdendencies so the next.config.ts was read either.

Once I realized that the app was build with cacheComponents: true and running with (effectively cacheComponents: false), it dawned on me the issue.

To be clear, this is user error, but I believe there is an opportunity for the docs and error messages to suggest this could be a cause.

Proposal

Update the docs per the above OR if possible, encode that the site was built with cacheComponents: true and fail if it is served with a different setting.