Have an "introspection" / "explainer" of why a check failed or succeded

[planchon]

Is your feature request related to a problem? Please describe.
In complexe ReBAC schemas, debugging failed / succeded check can be hard. Especially when you have a big number of node / vertices in your ReBAC schema.
I'm using the OSS software and I would like to have a way to understand why a check succeded or failed (at least in my local env, even better if possible in production)

Describe the solution you'd like
Some kind of endpoint I can query to have the reason why a check succeded or failed. I would supply the endpoint a check input and a date, then permify would do its magic and "explain" why what happen : why it succeded (or failed if possible).
More or less like the explain feature of SQL, but for Permify

Describe alternatives you've considered
Building it myself, but i dont think I have the time.