[android] Bookmark editor auto-closes after ~20 s during navigation

Describe the bug

While navigation is active, opening the bookmark/track editor (pencil icon in the Place Page) and not touching the map closes the editor by itself after ~20 seconds. Any text typed into the name/description fields is lost. The editor should stay open until the user closes it.

Steps to reproduce

1. Save a bookmark somewhere near your route.
2. Start navigation to any destination.
3. Tap the bookmark on the map to open its Place Page.
4. Tap the pencil (edit) icon and start typing a name/description.
5. Do not touch the map itself; wait ~20 seconds.

Expected: the editor stays open until the user saves or dismisses it. Actual: the Place Page and the editor dialog close on their own; typed text is lost.

Additional context

Traced statically, not yet verified on a device:

• During routing, MyPositionController::CheckNotFollowRouting() (libs/drape_frontend/my_position_controller.cpp:884) switches the map back to FollowAndRotate after kMaxNotFollowRoutingTimeSec = 20 s. The timer is only reset from FrontendRenderer::OnTouchEvent() (libs/drape_frontend/frontend_renderer.cpp:2246), i.e. by touches on the map surface — interacting with a dialog on top of the map does not reset it.
• On that mode change the core deactivates the current selection (libs/map/framework.cpp:1786: "Deactivate selection (and hide place page) if we return to routing in F&R mode"), which reaches Android as MwmActivity.onPlacePageDeactivated() → closePlacePage().
• The editor (EditBookmarkFragment) is a DialogFragment shown in the Place Page's child FragmentManager (PlacePageView.showBookmarkEditFragment()), so closing the Place Page destroys the open editor as well. The same applies to the other Place Page dialogs (colour picker, category chooser).

Auto-returning to follow mode is intentional; destroying a dialog the user is actively typing in is not. Possible fixes: block/reset the not-follow timer while a Place Page dialog is open, or avoid deactivating the selection while an editor is on screen.

The deactivation happens in shared core code, so iOS is likely affected too (unverified).