Fixes: #6490
Related to: #6339
Related to: #6421

This fix was originally applied with #6339 but was later reworked with #6421 (basically the part in frame.android.ts where disposing the fragments is performed after super.unloaded(...) logic).

The original fix did not work properly when called in onDestroyView(...) as it essentially removed the fragment view too early hence breaking exit transition. I actually tested onDestroy(...) then as well but due to a different bug addressed with #6421 and #6489 (essentially we need to cache and restore animators because of the simulated first navigation) onDestroyView(...) and onDestroy(...) were called at the same time (now onDestroy(...) is called after the actual exit transition is finished which means we can use it to detach the native view from its parent).