Don't conceal errors in resolvers for canFind, canModel and canQuery directives

[MarcEspiard]

• Added or updated tests
• Documented user facing changes
• Updated CHANGELOG.md

Context

While switching from @can to @canFind recently, we noticed that exceptions thrown from within a mutation class were caught and rethrown as generic AuthorizationException by the action: EXCEPTION_NOT_AUTHORIZED argument on can* directives.

This is an issue for our use case as we perform sanity checks (business logic) in the mutation code and throw specific exception / error messages back to the user in some cases.
We do want to use action: EXCEPTION_NOT_AUTHORIZED to hide ModelNotFoundException from end users, but we still need to return specific exception / message / error codes to the user manually (when the @can* directive actually passed) from the mutation class.

Changes

With this PR, I moved resolving the field to outside of the authorization try-catch block, when applicable.
I kept the changes non breaking.

Note (unchanged behavior):

1. Exceptions thrown in @canResolved are always caught / modified as resolving happens during the authorization.
   2.Exceptions throwing in @canRoot are never caught / modified as resolving happens before the authorization, outside of the try-catch

Unsure if this needs to be documented, happy to update the docs if needed?

Breaking changes

None

[spawnia]

Nicely done. What about adding tests for @canRoot? There is an existing CanRootDirectiveTest.

[spawnia]

Please fix https://github.com/nuwave/lighthouse/actions/runs/15428610746/job/43437901376?pr=2686.

[MarcEspiard]

Errors should be fixed and added an extra test for CanRoot

approved

[spawnia]

Released with https://github.com/nuwave/lighthouse/releases/tag/v6.58.0, thank you. Please consider sponsoring.

[MarcEspiard]

Thanks for the quick release!