fix: Handle DSN qs and show better error messages

[HazAT]

@kamilogorek fix tests plz

[getsentry-bot]

	Warnings
⚠️	Please add a changelog entry for your changes.

	Messages
📖	@sentry/browser bundle gzip'ed minified size: (ES5: 16.9883 kB) (ES6: 16.0391 kB)
📖	✅ TSLint passed

Generated by 🚫 dangerJS against 4c0260f

[Mnkras]

Just a heads up, this check broke some stuff we were doing with proxying requests.
We were using the projectid to route to different endpoints, and use strings that aren't only numbers.

[Ilko89BG]

(node:43) UnhandledPromiseRejectionWarning: SentryError: Invalid Dsn: Invalid projectId sentry
This what we have been getting after the release - I believe it has to do with this check!

[mitsuhiko]

@Ilko89BG can you share the DSN you're using?

[mitsuhiko]

So generally this has only been supported as an accident by this SDK. If you want to do something like this for routing where you cannot use an integer it would be better to use the path segment of a DSN which is supported.

So if you have https://key@server.tld/foobar as DSN you could use https://key@server.tld/foobar/1 instead (and use the 1 as a dummy project id).

[Ilko89BG]

@Ilko89BG can you share the DSN you're using?

'http://sentry@localhost/sentry'

So generally this has only been supported as an accident by this SDK. If you want to do something like this for routing where you cannot use an integer it would be better to use the path segment of a DSN which is supported.

So if you have https://key@server.tld/foobar as DSN you could use https://key@server.tld/foobar/1 instead (and use the 1 as a dummy project id).

Ok will try