feat(webview): add release() helper that detaches and destroys cleanly (#562)

[jim-daf]

Closes #562.

The StackOverflow answer linked in the issue boils down to: detach the WebView from its parent and call destroy() so Chromium can release its renderer process. Just letting the activity die leaks the surface and, on long sessions, eventually OOMs.

This PR adds an explicit release() helper on AwfulWebView that does the full cleanup dance (clear the JS interface so it does not retain the activity, navigate to about:blank, drop history, detach from parent, then destroy()). Hosting fragments and activities can call it from their own onDestroy / onDestroyView whenever they are sure they are done with the view.

public void release() {
    if (jsInterface != null) {
        removeJavascriptInterface(HANDLER_NAME_IN_JAVASCRIPT);
        jsInterface = null;
    }
    loadUrl("about:blank");
    clearHistory();
    ViewGroup parent = (ViewGroup) getParent();
    if (parent != null) {
        parent.removeView(this);
    }
    destroy();
}

Wiring the call sites is left out on purpose. The fragments that own a WebView each have their own teardown path, and rolling them all in one PR would balloon the diff.

[Copilot]

Pull request overview

Adds an explicit teardown helper to AwfulWebView intended to prevent long-session WebView/Chromium renderer leaks by performing a more thorough cleanup sequence before destroy().

Changes:

• Add AwfulWebView.release() helper to clear JS interface, navigate to about:blank, clear history, detach from parent, and destroy the WebView.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.