Identify the .mdx files affected in certain build errors

[ember-stevens]

Feature Description

Some build errors do not identify the .mdx files affected, and instead identify only line numbers. For example, I recently tried to build locally and received this error:

[docs]:Failed to read docs configuration. Rendering blank page.
[docs]:Expected a closing tag for `<Callout>` (22:1-22:127) before the end of `paragraph`

This message provides a line and column number, but no file identifier.

Use Case

Identifying the file names in error messages will greatly reduce the amount of troubleshooting needed to fix the error. In this case, I had opened a large PR with many callout changes so it was difficult to find the problem.

Proposed Experience (Optional)

Optionally, the error message would appear something like this:

[docs]:Failed to read docs configuration. Rendering blank page.
[docs]:Expected a closing tag for `<Callout>` (22:1-22:127) before the end of `paragraph` in home/topics/example.mdx`

Alternatives Considered (Optional)

No response