feat: add context to XML parsing errors

[yivi]

Whenever an XML parsing error is found, the error message will be something like:

[ERROR 1843] Element '{https://api-platform.com/schema/metadata/resources-3.0}operation': Character content other than whitespace is not allowed because the content type is 'element-only'. (in /var/www/ - line 28, column 0) in . (which is being imported from "/var/www/config/routes_api.php"). Make sure there is a loader supporting the "api_platform"
type.

Which is terribly unhelpful. The only file mentioned is in this case is a general routes configuration file, which is absolutely unrelated to the issue at hand.

Yes, ideally one wouldn't be modifying several configuration files at the same time, but sometimes it does happen.

This commit simply adds the path where the error was found to the error message, so now it becomes:

Error while parsing /var/www/src/config/api-platform/SomeResource.xml:
[ERROR 1843] Element '{https://api-platform.com/schema/metadata/resources-3.0}operation': Character content other than whitespace is not allowed because the content type is 'element-only'. (in /var/www/ - line 28, column 0) in . (which is being imported from "/var/www/config/routes_api.php"). Make sure there is a loader supporting the "api_platform" type.

Now the user knows the error happens on SomeResource.xml, and there is less frustration. :)

[alanpoulain]

LGTM

[soyuka]

This should target 3.0

[alanpoulain]

This should target 3.0

Not sure changing a message counts as a bug though.

[vincentchalamon]

OK for targeting main as it's not a bug IMHO

[alanpoulain]

Thanks @yivi.