fix: detail-page links stop going to dev.reactome.org + leave the pathway-browser cleanly when an author is clicked

Three bugs on the detail-page description panel (which is shared between
WebsiteAngular's /content/detail/* and the standalone PathwayBrowser app):

1. The dark-blue arrow icon in Events / Parent pathway / Components rows
   navigated to https://dev.reactome.org/... instead of the host the
   page was served from. environment.host in pathway-browser/environments/
   environment.ts was hardcoded to 'https://dev.reactome.org'; compute it
   from window.location.origin at module load so every URL built from it
   (CONTENT_DETAIL, CONTENT_SERVICE, ANALYSIS_SERVICE, DOWNLOAD, OVERLAYS,
   RESTFUL_API, CONTENT_QUERY) follows the current site. Same pattern as
   the earlier swagger and search same-origin fixes.

2. Author names under "Authorship" linked to /content/detail/<personDbId>,
   which hits the generic DetailComponent and renders an "entity not
   found" view -- Person records belong on /content/detail/person/<id>.

3. The three template links that hopped from pathway-browser to a
   /content/detail route used [routerLink]. That works when the
   description-tab is embedded inside WebsiteAngular's DetailComponent
   (same SPA, same router), but the standalone PathwayBrowser app
   (/beta/PathwayBrowser/ ...) is a separate Angular bundle with its
   own router that doesn't define /content/detail/* routes. The
   RouterLink fired, the URL changed, but PathwayBrowser's router
   matched no route so its components never tore down -- the user saw
   the new Person page rendered on top of leftover PathwayBrowser DOM
   ("Collapse all", download icons, etc).

   Switch all three links (Details-page button, inline PE link, author
   link) to plain [href]. Browser navigation is forced, which correctly
   unloads whichever Angular app was in front and loads WebsiteAngular
   at the new URL. The embedded use case eats a full reload instead of
   an SPA transition, which is acceptable for "leave the diagram"
   navigations.

Verified via Playwright on beta: a click on the first author from
/content/detail/R-HSA-164843 lands on /content/detail/person/73870 with
the person header rendered, zero leftover pathway-browser viewport DOM
in the result page. Also confirmed no remaining dev.reactome.org refs
in runtime source via grep, and that the existing /content/toc and
/content/doi author renderers already use the /person/ route.

Author: adamjohnwright

projects/pathway-browser/src/app/details/tabs/description-tab/description-tab.component.html

@@ -32,7 +32,7 @@
           </span>
       </div>
       <div class="details-button">
-        <a mat-button [routerLink]="`${CONTENT_DETAIL}/${obj().stId}`" target="_blank">
+        <a mat-button [href]="`${CONTENT_DETAIL_PATH}/${obj().stId}`" target="_blank">
           <mat-icon class="custom-icon double-arrow" [svgIcon]="'double-arrow-right'"></mat-icon>
           <span class="details-label"> Details page</span>
         </a>
@@ -249,7 +249,7 @@ <h4 class="facet-group-title">Disease status</h4>
         <div class="label-container">{{ item.key }}</div>
         <div class="composition-container">
           @for (pe of item.value; let i = $index; track pe.dbId) {
-            <a [routerLink]="`${CONTENT_DETAIL}/${pe.stId}`">{{ pe.name[0] }}</a>
+            <a [href]="`${CONTENT_DETAIL_PATH}/${pe.stId}`">{{ pe.name[0] }}</a>
             <!-- Add separator except for last item -->
             @if (i < item.value.length - 1) {
               <span class="margin-right">,</span>
@@ -317,7 +317,7 @@ <h4 class="facet-group-title">Disease status</h4>
           @for (ie of item.data; track $index) {
             <div class="authorship-item">
               @for (author of ie.author; let i = $index; track $index) {
-                <a [routerLink]="`${CONTENT_DETAIL}/${author.dbId}`"
+                <a [href]="`${CONTENT_DETAIL_PATH}/person/${author.dbId}`"
                    [ngClass]="{'margin-right': !author.orcidId}">
                   {{ author.firstname }} {{ author.surname }}
                 </a>

projects/pathway-browser/src/environments/environment.ts

@@ -1,6 +1,14 @@
+// Resolve the host from the browser's current origin so URLs built from
+// environment.host stay on whatever site the user is on -- beta.reactome.org,
+// release.reactome.org, reactome.org, localhost during dev. The fallback
+// applies when this module is imported in a non-browser context (e.g. unit
+// tests, build-time tooling) where window doesn't exist.
+const host: string =
+  typeof window !== 'undefined' ? window.location.origin : 'https://dev.reactome.org';
+
 export const environment = {
   production: false,
-  host: "https://dev.reactome.org",
+  host,
   s3: "https://download.reactome.org",
   gsaServer: "dev",
   gtagId: "G-96F1EYHQR3",