change(ios): better handling for keyboard stability after background restoration

[jahorton]

After a bit more searching... maybe I've found something this time?

• https://developer.apple.com/documentation/webkit/wknavigationdelegate/1455639-webviewwebcontentprocessdidtermi

We'd need to test and see if this is being called when our app is restored in this scenarios to be sure it's tied to the behavior that's been seen, of course.

Ref: ionic-team/capacitor#5488 (comment)

The thing we need to be sensitive to is that when a WebView background termination occurs, webViewWebContentProcessDidTerminate() is invoked when the app is coming back into the foreground [...]

Noting other issues from ionic and from react, they've seen cases where the WebView is 100% crashed, showing a blank page. We haven't had that issue, though we also aren't navigating across pages or doing other fancy web-server stuff on the back-end - it's just one page for us... albeit with a WebWorker backend and linked-in JS scripts. There's a fair shot that iOS's WebView is doing its best to restore our page after such a termination but is coming up short.

• Example react issue: Webview displays blank after going to background react-native-webview/react-native-webview#3062

One concerning thing here, though - these are big teams that are struggling to get this scenario right if this is indeed a match for our circumstances.

Originally posted by @jahorton in #10952 (comment)