Fail build if `pages` array in config references an unknown file

We had a case where someone accidentally changed a `pages` entry in the `.config.json` file to an empty string, and the build failed with a cryptic error message.  We should add a validation step that checks that each file exists in the `pages` array, and if not, produce a helpful error message.
