The Scope has a transaction field and it exposes a setter.

https://develop.sentry.dev/sdk/unified-api/#scope

This is now diverging because of the performance feature.
Should we keep it or not? does it get replaced by the performance feature or not?

on .NET
The transaction field still exists and coexists with the performance feature, they are totally separated features, they don't touch each other.

While on Java, the transaction does not exist anymore, it got replaced by the performance feature, which means, calling setTransaction on Java, reads the active transaction in the scope and overwrites its name.

We should document & unify this behavior.

@rhcarvalho @bruno-garcia @Tyrrrz @maciejwalkowiak @HazAT @brustolin