feat: Expose prio scope functions

[HazAT]

Counterpart to #2091

This exposes a new "global" functions from the Scope to provide a simpler API:

This enables users to do something like this:

Sentry.setTags({a: 'b'});
Sentry.setContext('os', {name: 'mac'});

// vs. 

Sentry.configureScope(scope => {
  scope.setTags({a: 'b'});
  scope.setContext('os', {name: 'mac'});
});

The motivation for this change is:

• Users don't need to fully understand the concept of a scope for the simplest use case there is e.g: setting tags Sentry.setTags({a: 'b'});
• This should provide users an easier path to migrate their old SDK codebase to the new one: string replace:

Raven.setTagsContext({a: 'b'}); 
// ->
Sentry.setTags({a: 'b'});

setXXX vs. configureScope

configureScope works differently in a way that in case there is no active client on the hub, the configureScope callback will not be invoked at all, meaning if there are expensive operations this is better than setXXX.

[dcramer]

isnt this setExtra? and extra?

[HazAT]

Good point, before we only had setExtra on the scope which allowed only key:value setExtras allowed to set an object.

I will change that it accepts both.

[dcramer]

👍 i think its fine though i would probably want to override the entire extra per old functionality (for other things folks should probably just use setContext)

[HazAT]

Maybe, we should even consider not even exposing setExtra at all anymore.
Could be too early tho, I mean it's still there in configureScope but not on Sentry.set...

[kamilogorek]

You cannot have multiple input types in Go, so I'd still need to have 2 methods for it

[getsentry-bot]

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

Generated by 🚫 dangerJS against 25c7558

[kamilogorek]

Looks good. The only change that I'd like to make in this PR as well is remove client guard from configureScope, as it's not client dependent. Once it's added, feel free to merge.

[G-Rath]

Don't mean to hijack, but:

configureScope works differently in a way that in case there is no active client on the hub

When would you not have an active client? I'm guessing maybe if you don't provide a DSN value? (which is the official way to handle enabling & disabling Sentry between environments, such as for local development, iirc).

Might be useful to note that in the documentation somewhere, if it's not already (not that I think people should be encouraged to make expensive/complex operations for Sentry data if they can avoid it 😂)

(Also, I think you might have forgotten about exposing clearScope 😉 )