Improve error output for schema validation workflow

[moonlight-komorebi]

Summary

It was pointed in recent failures that the output produced when the validation workflow fails is not helpful. Here is a link to the failing workflow: example, and the error output is:

 Error: packs/mlops/algorithmia/dashboards/algorithmia.json
	 must be string
	 must match a schema in anyOf

The output isn't always this unfriendly, it just depends on the specific error that is encountered. In general, we want to improve the output so that no matter the error the output generated points you to the error location, and a potential fix.

Before we start this work, we should identify the specific failure cases that we want to test for so that we can take a more rigorous approach this time around.

Acceptance Criteria

• [ ] TBD

[github-actions[bot]]

Old issues will be closed after 105 days of inactivity. This issue has been quiet for 90 days and is being marked as stale. Reply here to keep this issue open.

[jpvajda]

@nr-kkenney do we still need to be concerned with this? I felt we did some improvement to error messages, but wasn't sure if we resolved this.

[moonlight-komorebi]

@jpvajda yes / no. i think we handled a couple specific cases (like this one), but I imagine this could still crop up. Especially since we are going to switch how we validate.

But that can live in a new ticket, or a ticket can be created on a case by case basis based on what we see.

[github-actions[bot]]

Old issues will be closed after 105 days of inactivity. This issue has been quiet for 90 days and is being marked as stale. Reply here to keep this issue open.

[github-actions[bot]]

This issue is being closed due to inactivity. Is this a mistake? Please re-open this issue or create a new one.