[AlexAndBear]

Description

• Admin Users search: browser Back and Forward now update the search input and the user list when the search term in the URL changes.
• Selection: a Back/Forward search change resets the selection, so a user who drops out of the list isn't acted on.

A search on a page without page in the URL still creates two history entries (search push plus page push), so the first Back only removes page. This is fixed by #3699, which resets the page with router.replace.

Related Issue

• Fixes The user search term in admin Users doesn't follow browser Back #3750

How Has This Been Tested?

• test environment: unit tests (Vitest), browser tests (Playwright) against a local OpenCloud
• test case 1: removing the search term from the route clears it and reloads the users
• test case 2: a route-driven search change resets the selection
• test case 3: browser: search, Back, Forward; one load per step; selection reset

Types of changes

• Bugfix
• Enhancement (a change that doesn't break existing code or deployments)
• Breaking change (a modification that affects current functionality)
• Technical debt (addressing code that needs refactoring or improvements)
• Tests (adding or improving tests)
• Documentation (updates or additions to documentation)
• Maintenance (like dependency updates or tooling adjustments)