Always remove cached exclusion regions when display removed

It is very likely that windowManager.unregisterSystemGestureExclusionListener will fail during #onDisplayRemoved the callback is async and it's likely that DisplayContent is already gone. So whether the WindowManager call succeeds or not we will update the exclusion regions cache. This also updates the Logcat so that it no longer prints the stacktrace as it creates a red herring that a crash happened even though it was caught.

Bug: 417280112
Bug: 425714615
Test: Manual and build
Flag: EXEMPT bugfix
Change-Id: Ia4fbdc5ebce4a25b21b591009bcc3d08583f881f