microG crashed after closing game quickly

Nobody has claimed this yet.

**Describe the bug**
microG crashed

**To Reproduce**
Steps to reproduce the behavior:
1. Open game
2. Close game quickly
3. See error

**Expected behavior**
No crash

**System**
Android Version: 15 QPR2
Custom ROM: LineageOS 22.2

**Additional context**
```
04-29 21:48:21.321 3036 3036 E AndroidRuntime: FATAL EXCEPTION: main
04-29 21:48:21.321 3036 3036 E AndroidRuntime: Process: com.google.android.gms, PID: 3036
04-29 21:48:21.321 3036 3036 E AndroidRuntime: android.os.DeadObjectException
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at android.os.BinderProxy.transactNative(Native Method)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at android.os.BinderProxy.transact(BinderProxy.java:592)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at com.google.android.gms.games.internal.connect.IGamesConnectCallbacks$Stub$Proxy.onSignIn(IGamesConnectCallbacks.java:101)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at org.microg.gms.games.GamesConnectServiceImpl.signIn$sendSignInRequired(GamesConnectService.kt:71)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at org.microg.gms.games.GamesConnectServiceImpl.access$signIn$sendSignInRequired(GamesConnectService.kt:54)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at org.microg.gms.games.GamesConnectServiceImpl$signIn$sendSignInRequired$1.invokeSuspend(Unknown Source:13)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at kotlinx.coroutines.internal.DispatchedContinuation.resumeWith(DispatchedContinuation.kt:204)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at kotlin.coroutines.SafeContinuation.resumeWith(SafeContinuationJvm.kt:41)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at org.microg.gms.games.GamesConfigurationService$Companion$singleRequest$2$connection$1$onServiceConnected$1.handleMessage(GamesConfigurationService.kt:179)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:109)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:232)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at android.os.Looper.loop(Looper.java:317)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8934)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:591)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:911)
04-29 21:48:21.321 3036 3036 E AndroidRuntime: Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@ec7a2e0, Dispatchers.Main.immediate]
```

Start with org.microg.gms.games.GamesConnectService.kt around line 71 and trace the request flow through GamesConfigurationService.kt around line 179. Reproduce the crash by opening a game and closing it quickly on the reported Android setup, then investigate the DeadObjectException. Done means this sequence no longer crashes microG.

Written by the indexing model from the issue text.