`AutoSessionTracking` without file persistency

### Question
Does the `GlobalSessionManager` function as intended when `FileWrite` is disabled?

### Challenges Without File Write
1. **Crash-Free Rate Inaccuracy**:
- Without persistence, crashes that completely terminate the process cannot be reported.
- This results in a misleadingly high crash-free rate metrics.

2. **Impact on `Release Health`**:
- The purpose of `Release Health` is to measure application stability using session tracking.
- We cannot measure stability if we cannot persist across application runs.

### Conclusion
Without access to file write, the core functionality of session tracking is not really possible. I think we should disable/opt-out of the integration in those cases.