The active menu trail does not respect query strings when several menu links share the same route

Problem/Motivation

When several menu links point at the same route and differ only by their query string, the active trail always resolves to the same menu link, no matter which of them the visitor actually followed. The wrong parent menu item is highlighted.

With the merge request from #2845319 applied, the correct child link receives is-active while the wrong parent is still highlighted, because in_active_trail is computed on a separate code path that the merge request does not touch.

Steps to reproduce

1. Create a menu structure similar to this:
-- Parent A > /all-topics
---- Child A > /all-topics?foo=1
-- Parent B > /node
---- Child B > /all-topics?foo=2
2. Visiting Child A will mark the link as is-active and the Parent A as active
3. Visiting Child B will mark the link as is-active and Parent A as active

Expected: Parent B should be marked as active when visiting Child B.
Actual: Parent A is marked active when visiting Child B.

Proposed resolution

When more than one menu link matches the current route, prefer the link whose query options are all present in the current request. Fall back to the current behaviour when none match.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet