Avoid stringify if log levels are not met

[SebC99]

New Issue Checklist

• [x ] I am not disclosing a vulnerability.
• [ x] I am not just asking a question.
• [ x] I have searched through existing issues.
• [ x] I can reproduce the issue with the latest version of Parse Server.

Issue Description

Sorry I don't have the time for a PR as I struggle with my day-to-day job, but as I told @mtrezza I think we can have a significant performance increase by rewriting the logTriggerSuccessBeforeHook and logTriggerErrorBeforeHook functions.
In both cases, these methods stringify the Parse Object (request & response) before checking for the log level.
As JSON.stringify is one of the most CPU-intensive (and one of the slowest) methods of Parse, I guess checking for log level first would be better.

[parse-github-assistant]

Thanks for opening this issue!

• ❌ Please edit your post and use the provided template when creating a new issue. This helps everyone to understand your post better and asks for essential information to quicker review the issue.