chore(replay): use INTERNAL_API_SECRET for rasterizer recording-api auth

[TueHaulund]

Summary

• Use INTERNAL_API_SECRET env var consistently for recording-api authentication in the rasterizer, matching the charts config (secret_env: INTERNAL_API_SECRET: INTERNAL_API_SECRET)
• Removes the old RECORDING_API_SECRET reference — a single consistent name across all services

Test plan

• Verify rasterizer pods start without CreateContainerConfigError after charts PR feat: new sort filter for taxonomic filter #9271 is merged
• Run a rasterize-recording workflow and confirm it no longer fails with [INIT_FAILED] Failed to fetch

[greptile-apps]

Comments Outside Diff (1)

1. bin/temporal-recording-rasterizer-worker, line 83 (link)

   Stale env var name in local dev script

   config.ts now reads INTERNAL_API_SECRET, but this script still injects the variable under the old name RECORDING_API_SECRET. The container will receive the secret under a name it no longer looks for, so config.recordingApiSecret will always be an empty string in local development — breaking the rasterize-recording workflow for anyone running this script locally, for the same reason the charts deployment was broken before the charts PR fix.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: bin/temporal-recording-rasterizer-worker
   Line: 83
   
   Comment:
   **Stale env var name in local dev script**
   
   `config.ts` now reads `INTERNAL_API_SECRET`, but this script still injects the variable under the old name `RECORDING_API_SECRET`. The container will receive the secret under a name it no longer looks for, so `config.recordingApiSecret` will always be an empty string in local development — breaking the rasterize-recording workflow for anyone running this script locally, for the same reason the charts deployment was broken before the charts PR fix.
   
   How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: bin/temporal-recording-rasterizer-worker
Line: 83

Comment:
**Stale env var name in local dev script**

`config.ts` now reads `INTERNAL_API_SECRET`, but this script still injects the variable under the old name `RECORDING_API_SECRET`. The container will receive the secret under a name it no longer looks for, so `config.recordingApiSecret` will always be an empty string in local development — breaking the rasterize-recording workflow for anyone running this script locally, for the same reason the charts deployment was broken before the charts PR fix.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "chore(replay): use INTERNAL_API_SECRET f..." | Re-trigger Greptile}