Error stack trace missing from api side log formatter when masking GraphQL errors

[dthyresson]

A fix for the logger was made after the GraphQL Yoga release that reinstated the error message when an error is masked in th GraphQL Server: #4912

That PR was favored over #4902 which has a similar fix.

The 4912, however, the original error's full stack trace is no longer output when logging.

While the error message is provided, the stack trace on the api side can be helpful in tracking down the line that raised the error and help debug and fix.

The approach in 4902 should be revisited as it adds to complete original error details into the error -- and should check that the RedwoodLogger presented that stack trace as well.