Possible issue routing events to the wrong Sentry project when multiple project DSNs are used

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

I would like to understand whether it is possible for Sentry events to be associated with the wrong project, particularly when multiple Sentry projects exist for different environments (e.g., Development and Production).
We are currently observing what appears to be unexpected behavior where issues originating from our Production environment are appearing in the Development project's issue list.

Environment

- Sentry Business subscription
- .NET MAUI application
- Recently upgraded from .NET 8 to .NET 10
- Upgraded Sentry SDK from an older version to Sentry .NET MAUI SDK 6.0.0

What we have verified

- Each environment has its own dedicated Sentry project.
- Production and Development projects have different DSNs.
- Build configurations are correctly configured to use the appropriate DSN for each environment.
- We have verified the DSN embedded in the Production build points to the Production Sentry project.
- We have also verified the Development build points to the Development Sentry project.
- This setup worked correctly prior to upgrading the application and Sentry SDK.
-

Questions

Is there any known issue in the Sentry .NET MAUI SDK 6.0.0 that could result in events being sent to the wrong project?

Is there any scenario where Sentry could associate events with a project other than the one specified by the DSN?

Are there any known issues related to project routing, environment tagging, caching, SDK initialization, or project identification that could explain Production events appearing in the Development project?

Are there specific diagnostics or event metadata we should inspect to determine how these events were routed?

At the moment, we have not found any configuration issues on our side, and the behavior appears inconsistent with how the system operated before the SDK upgrade. Any guidance on potential causes or recommended troubleshooting steps would be appreciated.

### Expected Result

Events generated by the Production application should only appear in the Production Sentry project, and events generated by the Development application should only appear in the Development Sentry project, based on the configured DSN for each environment.

### Actual Result

We are observing events and issues that appear to originate from the Production application showing up in the Development Sentry project's issue list. We have verified that each environment is configured with a unique DSN and that the correct DSN is being used at build time. This behavior was not observed prior to upgrading to .NET 10 and Sentry .NET MAUI SDK 6.0.0.

### Product Area

Issues

### Link

_No response_

### DSN

_No response_

### Version

_No response_