ref(issue-details): replace useRouter with specific hooks in useGroupDetailsRoute

[evanpurkhiser]

Part of the React Router 6 cleanup — replaces useRouter() with specific hooks (useNavigate, useLocation, useParams, etc.)

[sentry]

Bug: The getCurrentTab function always defaults to the 'Details' tab because route objects are missing the handle.path property, causing currentRoute.path to be an empty string.
_{Severity: HIGH}

Suggested Fix

Update the route definitions for the issue detail tabs to include a handle object with a path property that mirrors the existing path value. For example, a route with path: TabPaths[Tab.ACTIVITY] should also have handle: { path: TabPaths[Tab.ACTIVITY] }. This will ensure useRoutes() correctly populates the path property on the route object, allowing getCurrentTab() to identify the active tab.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: static/app/views/issueDetails/useGroupDetailsRoute.tsx#L37-L41

Potential issue: The `useRoutes()` hook creates route objects where the `path` is
derived from `match.handle?.path ?? ''`. However, the route definitions for the issue
details tabs do not include a `handle` object with a `path` property. Consequently, when
`getCurrentTab()` runs, the `currentRoute.path` is always an empty string. The logic to
find the active tab, `Object.values(Tab).find(tab => currentRoute?.path ===
TabPaths[tab])`, will always fail to find a match, causing it to fall back to the
default `Tab.DETAILS`. This prevents the UI from correctly highlighting the active tab
on the issue details page.

_{Did we get this right? 👍 / 👎 to inform future reviews.}