feat: Sentry logs

[PatrickJS]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/scullyio/scully/blob/main/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Other... Please describe:

What is the current behavior?

no error logging for the cli or docs

Issue Number: N/A

What is the new behavior?

error logging for the docs and cli

Does this PR introduce a breaking change?

• Yes
• No

Other information

fixes #783

[SanderElias]

Looks good to me. A couple of questions left.

1. Is the logging of errors optional in the CLI? I seem to have missed the option to opt-out
2. There are a couple of calls that have the 'suppressError' option. That means the call will never fail. yet you have added the sentry stuff there.
3. The key for sentry seems hardcoded in Scully? shouldn't we use an environment var or something?
4. can you explain the flush in pluginwrap.ts? I think it's not needed. The pluginsError is an option that when set, the program exists. Normally it just ignores plugin errors and carries on. (perhaps handle the flush in 'launchedBrowser.ts` where the whole exit is handled?

[amycdurbin]

@aaronfrost should we make this mandatory?

[aaronfrost]

@amycdurbin should we make WHAT mandatory? That they opt into errors? Yes. It is not required to get permission for errors (I was told by Patrick). It is, however, required to get permission for telemetry data. So these errors are not telemetry. So let's do it.

Also, let's get this merged already... I want to see the errors that the users are seeing. We are wasting daylight by not merging this PR. Get it done already.

[amycdurbin]

@amycdurbin should we make WHAT mandatory? That they opt into errors? Yes. It is not required to get permission for errors (I was told by Patrick). It is, however, required to get permission for telemetry data. So these errors are not telemetry. So let's do it.

Also, let's get this merged already... I want to see the errors that the users are seeing. We are wasting daylight by not merging this PR. Get it done already.

@SanderElias please see Frosty's response.

[SanderElias]

@aaronfrost I'm pretty sure collecting any data (including errors) from a user's system goes right into GRPD.
Or at least it will be frowned upon, and lead to questions that are easily avoided.