Parent #17173

This issue is about resolving the getFragmentManager(...) and requireFragmentManager() compile warnings for the WordPress module, and possibly, for the lib modules as well.

PS: Some of those warnings are already deprecated (see here).

• This getFragmentManager(...) method is deprecated. This has been removed in favor of getParentFragmentManager() which throws an IllegalStateException if the FragmentManager is null. Check if isAdded returns false to determine if the FragmentManager is null.
• This requireFragmentManager(...) method is deprecated. This has been renamed to getParentFragmentManager() to make it clear that you are accessing the FragmentManager that contains this Fragment and not the FragmentManager associated with child Fragments.

For more info see:

• Fragment.getFragmentManager
• Fragment#.requireFragmentManager