fix(test): handle deduped events when collecting - #1066

I don't think nimble_ownership needs to be a regular dep if it's only used in Sentry.Test code. Following that logic would bypass also become a regular dep now? I don't want to have to ship cowboy in my bandit based Phoenix project :)

Instead, if start_collecting_sentry_reports is going to be still supported, I would suggest adding the same helpful runtime errors to it that setup_sentry has, basically this line to improve DX

I don't think nimble_ownership needs to be a regular dep if it's only used in Sentry.Test code

I 100% agree - unfortunately this is how it used to be in pre-13.0.0 releases and because I added it back, the dep needs to be back too, otherwise it'd be a breaking change and I'd have to release 14.0.0 already 😢

Following that logic would bypass also become a regular dep now? I don't want to have to ship cowboy in my bandit based Phoenix project :)

Nope. We happen to use bypass but it's going away in 14.0.0 in favor of a new built-in abstraction (possibly a test transport or maybe just a test http client that captures requests for assertions, not sure yet).

Instead, if start_collecting_sentry_reports is going to be still supported, I would suggest adding the same helpful runtime errors to it that setup_sentry has, basically this line to improve DX

Thank you. This crossed my mind but then I realized that, as I explained above, sticking to only: [:test] would be a breaking change. Existing test suites that use 13.0.0 must continue to work when upgrading to 13.1.0.