Investigate auto-instrumentation limitation using IITM for meta-frameworks

We have an issue where modules are not being patched correctly in meta-frameworks. This prevents users from getting AI integrations out of the box and forces them to use manual instrumentation.

Core problem: auto-instrumentation fails because meta-frameworks import modules **before** they are registered with the `import-in-the-middle` hook system. Meta-frameworks often parse files to discover routes, which triggers top-level imports. As a result, AI SDKs load before Sentry can register and patch them.