[FR] Better Error Messages for Schema Validation

[eric-forte-elastic]

Is your feature request related to a problem? Please describe.
Is it currently difficult to debug situations where there is a schema violation due to the error message being difficult to read.

Describe the solution you'd like
I would like that when a schema error is encountered, it displays the specific error that is the source of the issue either at the end or separate from other irrelevant errors that are triggered as a result of the first violation.

Additional context
See this issue #3542 as an example. The error message in this case should be informing the user that the name is in violation of the schema. While that error is in the list of errors in the message, it is very difficult to tell which one is the ultimately contributing error.

[Mikaayenson]

This may be a duplicate or overlap with #3195

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.