Syntax errors aren't logged correctly in LiveQuery triggers

[dblythy]

New Issue Checklist

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

Issue Description

When a syntax error is recorded in either a beforeConnect, beforeSubscribe, or afterLiveQueryEvent trigger, the error is logged without any useful infomation to help diagnose.

Steps to reproduce

Create a LQ trigger with a JS error.

Actual Outcome

Failed running beforeConnect for session undefined with:
     Error: {}

Expected Outcome

Failed running beforeConnect for session undefined with:
     Error: foo is undefined

Environment

Server

• Parse Server version: master
• Operating system: macos
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): local

Database

• System (MongoDB or Postgres): mongo
• Database version: 5
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): local

Client

• SDK (iOS, Android, JavaScript, PHP, Unity, etc): JS
• SDK version: master

Logs

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.