Fix bivariance issues in Sentry.Options TS type

[twavv]

Fixes #4233 (at least in just this one file -- haven't checked anything else, but this seems like the most important since it's the place people are most likely to pass in their own functions).

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

• If you've added code that should be tested, please add tests.
• Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

[AbhiPrasad]

Awesome, thank you for your contribution!

The only concern here would be if many users would have to make code changes after we change the typing, but I guess that is also dependent on them using — strictFunctionTypes. If this is the case though, we probably have to save the change for a major bump to reduce friction for sdk users.

What do you think?

[twavv]

I'd be inclined to just release with a patch bump but I don't have strong opinions. I doubt the majority of people are impacted by this (and if they are, then it's ostensibly a bug in their code).

[AbhiPrasad]

I'd be inclined to just release with a patch bump but I don't have strong opinions. I doubt the majority of people are impacted by this (and if they are, then it's ostensibly a bug in their code).

Yeah we discussed internally and came to a similar conclusion.

We probably will add a custom eslint rule to catch these cases (methods under publically exported types/interfaces)

For now let's ship this and improve as we go!