Auto-isolate asyncio tasks if event loop is running

Currently, the opt-in `AsyncioIntegration` is responsible for multiple things, one of them being providing proper scope isolation in asyncio tasks. Without this functionality, people are running into different types of hard-to-diagnose scope bleed issues, like [here](https://github.com/getsentry/sentry-python/issues/5352).

### Goal
- Automatically patch the current event loop to isolate tasks in their isolation scopes, if there is an event loop running
- For additional functionality (creating task spans, etc.), explicit opt-in should still be required from users

### How to do this

Different ways to do this, each with its own caveats (e.g. introducing breaking changes).

1. Take the isolation scope logic out of `AsyncioIntegration` into its own integration and make it auto-enabled (best effort, if there is no event loop we can't do anything).
2. Make `AsyncioIntegration` auto-enabled, and change the additional functions it's providing (like task spans) to be opt-in. Also, make it fail gracefully if there is no event loop to patch.
3. ???

When picking an option, consider:
- Will this break behavior for existing users using the `AsyncioIntegration`?
- Is there a risk of double-patching the event loop?

先閱讀現有的 AsyncioIntegration 及其隔離作用域行為，然後比較提議的自動啟用設計。檢查如何對正在執行的事件迴圈進行修補、是否可以重複修補，以及這會如何影響現有的 AsyncioIntegration 使用者。完成的標準是任務隔離能夠自動運作，同時附加功能仍需明確 opt-in，並且在沒有事件迴圈的情況下能夠優雅地失敗。

由索引模型根據 Issue 內容生成。