Log where module failures occur

Currently, when `attw` fails, the error message may look something like,

> A require call resolved to an ESM JavaScript file, which is an error in Node and some bundlers. CommonJS consumers will need to use a dynamic import. https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/CJSResolvesToESM.md.

The immediate question that comes to mind is: *where is the import causing the failure*? It would save considerable time and add clarity to the error message if the location of the incorrect module import was logged.

Start by reproducing the reported attw failure and trace how the current module-resolution error is assembled. Identify where the incorrect module import can be observed; done means the failure message logs that import location while preserving the existing diagnostic.

Written by the indexing model from the issue text.