Lighthouse should not return the 'data' key if an exception was thrown in the custom builder

Are you willing to provide a PR for this issue or aid in developing it?
No, I do apologize.

What problem does this feature proposal attempt to solve?
I am using the paginator directive with the builder parameter for a field as such:
@paginate(builder: "App\\GraphQL\\Builders\\foo@bar")

and in the bar function (probably mistakingly) I check the user permissions before returning the query builder:

public function bar($root, array $args, GraphQLContext $context, ResolveInfo $resolveInfo): Builder
{
   if ($context->user->can('Foo Bar')) {
      return Model::query();
   } else {
      throw new Unauthorized();
   }
}

And this works fine (sort of) in the way that the error is displayed correctly but a null data section is also returned:

{
  "errors": ["CORRECT EXCEPTION HANDLING"],
  "data": {
    "Query name": null
  }
}

Which possible solutions should be considered?
If an exception was thrown during a custom builder, Lighthouse should not return the data key in the results.

Reproduce the reported @paginate query with a custom builder that throws Unauthorized, then trace the paginator and GraphQL response error-handling path. Add regression coverage for the exception case; done means the errors remain present while the response omits the data key.