Review creation of unbound coroutine scopes

[TimoPtr]

Description

In the app we have a common pattern of creating ioScope that are basically a simple scope without lifecycle. This is nothing more than a GlobalScope in the end. One issue with this pattern is that we are creating many scopes and most of the time we mostly ignore that it is not tight to a lifecycle and we probably shouldn't ignore this.

In the scope of this task we should review the creation of scopes and decide if the creation of a scope is relevant

• Can we tight it to a lifecycle?
• Is there a risk to use the GlobalScope (potential crash of the application?)

Additional context

No response