Add a stackFrameFilter argument to SentryClient's capture

[tom95]

This change allows filtering sensitive frames on the client or applying custom truncation logic.

I created this in reaction to this discussion: https://forum.sentry.io/t/issue-in-flutter-project-with-stackframe-display-limit-set-to-250/5014/2

Instead of adding complex truncation options that will likely depend on the frameworks you use anyways, I opted to provide a more general callback that could also be used for things like filtering specific frames. In the case of above discussion, we'd simply cut the list passed to us to only send the topmost 250 items.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[tom95]

I signed it!

[yjbanov]

This repository was supposed to be moved under https://github.com/flutter/packages but we somehow ended up in a situation where this repository was erased but the other one not populated. I'll find out what's going on. Thanks for the PR! We'll find a way to accept it, hopefully soon 😃

[tom95]

Alright, I was wondering about that :D Please tell me once you figured out where the code should go, I also realized that I have the wrong mail address for the CLA in the commit's stamp, so I'll have to replay the changes anyways.

[yjbanov]

@tom95 The repository has been restored. Could you please rebase to kick off Travis and correct the email address for the CLA bot to recheck it?

[tom95]

I signed it!

[tom95]

Well not entirely sure what's missing now. Mail on the commit should be correctly ending in "@4ed1.com" and it's been added to my github account as well. The corporate CLA has also been signed.

[yjbanov]

Maybe it will help if you open a new PR with a freshly authored commit that contains the correct email? Just guessing.

[tom95]

I signed it!

[googlebot]

CLAs look good, thanks!

[tom95]

Hey, what's the status of the PR? Should it be held up by the failing travis build, I am hoping that's just because at the time of the build the CLA was not accepted, at least the log only says "presubmit" failed.

[yjbanov]

The CLA is happy with both this PR and #30. Let's close one and merge the other?