Browser tab title is static instead of reflecting page context

What steps does it take to reproduce the issue?

1. Open the React version of Dataverse.
2. Navigate between different pages/contexts: the home page, a collection page, a dataset page, a file page, the login page, search results, account page, etc.
3. Observe the browser tab title in each case.

When does this issue occur?

On every page load/navigation in the React frontend.

Which page(s) does it occur on?

All pages. Confirmed static on the home page (shows repository/root collection name regardless of context) and the login page (doesn't indicate you're on the login page). Based on the legacy JSF behavior, this likely affects every page type, including: collection pages (root and sub-collections), dataset pages, file pages, login page, account/profile page, search/advanced search, permissions management pages, dashboard/admin pages, and error pages (404/403/500).

What happens?

The browser tab title never changes — it always shows a single static value (the repository/root collection name), no matter what page or object the user is viewing.

To whom does it occur (all users, curators, superusers)?

All users — this is frontend routing/rendering behavior, not permission-dependent.

What did you expect to happen?

The tab title should update dynamically per page/context, mirroring the legacy JSF app's behavior:

• Root collection (home) page: the collection's name alone (e.g., Demo Dataverse).
• Sub-collection page: that collection's own name alone (e.g., Sub Collection) — does not include the parent/root name.
• Dataset page: {dataset title} - {parent dataverse name} (e.g., Replication Data for: Foo Study - Demo Dataverse).
• File page: {filename} - {containing dataverse name} (e.g., data.tab - Demo Dataverse).
• Login page: Log In - {root dataverse name} (e.g., Log In - Demo Dataverse).
• Other pages (account, search, permissions, dashboard, error pages, etc.) generally follow {action/page label} - {contextual or root dataverse name} (e.g., Advanced Search - Demo Dataverse, 404 Not Found - Demo Dataverse).

In the legacy JSF app, each page defines its own title via a pageTitle template parameter rather than one fixed value, so the pattern is not perfectly uniform across every page — but the general rule is: the tab title always reflects the current page/object, with the containing dataverse's name commonly appended for dataset/file/utility pages.

Start in the React frontend's routing and page-rendering entry points, comparing title behavior across the home, collection, dataset, file, login, search, account, permissions, dashboard, and error contexts listed in the issue. Use the legacy JSF title behavior as the reference, and consider the work done when each page context displays the appropriate contextual browser tab title.