Log document id when MapperParsingException occurs

[dr0i]

Resolves #37658.

[elasticmachine]

Pinging @elastic/es-search

[mayya-sharipova]

@elasticmachine test this please

[mayya-sharipova]

@elasticmachine test this please

[mayya-sharipova]

@elasticmachine test this please

[dr0i]

@mayya-sharipova as you see I had some problems with testing. I added two commits and you started the integration test again, thanks !

If I locally test everything with ./gradlew check, it fails because of TransportException and such. The automatic build tests also fail with these errors.
But I don't think this is because of my changes (logging an ID).
So I test only the package which tests the affected code (EDIT: after rebasing my branch to be up-to-date):
./gradlew --debug cleanTest "-Dtests.class=org.elasticsearch.index.mapper.*"
This results in BUILD SUCCESSFUL.
I also had a quick look at others' PR and there it also seems often the case that the whole testing don't work. Can you help me get things straight?

[dr0i]

Uh - ./gradlew check works now - no more TransportExceptions. Hopefully these are also gone when the automatic tests by elasticmachine are executed.
(What I changed: 1. rebased to newest master ; 2. used an other machine). Maybe the cause was e.g. #37893 et al, where tests randomly failing and are mow muted in the tip of the newest master.

[mayya-sharipova]

@elasticmachine test this please

[mayya-sharipova]

@elasticmachine test this please

[mayya-sharipova]

@dr0i Thank you for your PR, it is approved! I will try to monitor the CI build, and once all the tests are passed, I will merge your PR to the upstream master.

[dr0i]

@mayya-sharipova great, thx !