Please consider making ignoreSentryErrors on Sentry.AWSLambda.wrapHandler true by default

[kitsunde]

We seem to have gotten bit by #4582 where suddenly sentry's 429 rate-limiting is the cause of our backend downtime.

The only change we made was upgrading from using our own lambda layer which was pinned as 6.2.5 to the official one.

I'm not sure how this could've been caught before deployment since we would've needed to effectively simulate sentry's rate limiting on lambda, so ignoreSentryErrors defaulting to false seem like the unsafe option, and needs to be remembered every time Sentry is setup.

[vladanpaunovic]

Thanks @kitsunde, there is a PR #4994 on it's way at the moment to resolve this in our next major version v7.

Meanwhile, you can use a solution shown in the PR example.