Add @sentry/browser as a peer dependency or a range

[darkowic]

Hello! Instead of forcing to install the latest @sentry/browser, allow choosing version by adding a sentry browser as a peer dependency or at least a range of supported versions. With it, we can avoid some unexpected breaking changes.

[ReDrUm]

+1 to this. The current approach results in a warning like this:

warning Pattern ["@sentry/browser@latest"] is trying to unpack in the same destination "/Users/person/Library/Caches/Yarn/v6/npm-@sentry-browser-5.16.1-7a5ad85d9002de1495b1f63c3a4edb688a27f644-integrity/node_modules/@sentry/browser" as pattern ["@sentry/[email protected]"]. This could result in non-deterministic behavior, skipping.

@sentry/browser@latest is actually 6.x rather than 5.x at this point in time, making the yarn lock files that have grouped latest with the 5.x range inaccurate as soon as 6.x+ was released.