fix(content-server): Enable esbuild-register for server-side @fxa/shared imports

Because:
- content-server's server/bin and server/lib now require @fxa/shared/*
  modules that aren't reachable via normal node resolution. auth-server
  and others already run under 'node -r esbuild-register', which ships
  tsconfig-paths and maps those imports. content-server was starting
  with plain 'node ...', so the server refused to boot in CI — causing
  Playwright 'NS_ERROR_CONNECTION_REFUSED to http://localhost:3030/'.
- Content-server's own tsconfig.json sets baseUrl to ./app/scripts for
  the Backbone bundle, which broke the paths resolver even with
  esbuild-register. TS_NODE_BASEURL=../../ pins tsconfig-paths back to
  the repo root at runtime without affecting the webpack build.

This commit:
- Adds -r esbuild-register to the pm2 startup command
- Sets TS_NODE_BASEURL=../../ so @fxa/* paths resolve to libs/

Author: dschom

packages/fxa-content-server/pm2.config.js

@@ -11,7 +11,8 @@ const apps = [];
 
 apps.push({
   name: 'content',
-  script: 'node --inspect=9130 server/bin/fxa-content-server.js',
+  script:
+    'node --inspect=9130 -r esbuild-register server/bin/fxa-content-server.js',
   cwd: __dirname,
   watch: ['server/**/*.js', 'server/**/*.html', 'server/**/*.json'],
   env: {
@@ -24,6 +25,7 @@ apps.push({
     SENTRY_DSN: process.env.SENTRY_DSN_CONTENT,
     TRACING_SERVICE_NAME: 'fxa-content-server',
     TRACING_CLIENT_NAME: 'fxa-content-client',
+    TS_NODE_BASEURL: '../../',
   },
 });