JavaScript heap OOM during catch-up sync

### Describe the bug

Running Lodestar via the packaged binary appears to hardcode:

--max-old-space-size=8192

which overrides NODE_OPTIONS and prevents increasing the Node.js heap size during sync.

Environment:
* Install method: packaged binary in /usr/local/bin/lodestar
* Network: mainnet
* OS: 24.04
* Deployment: LXC

Systemd service includes:

Environment=NODE_OPTIONS=--max-old-space-size=16384

Verified present in process environment:

cat /proc/$(pgrep -fn lodestar)/environ | tr '\0' '\n' | grep NODE_OPTIONS

Output:

NODE_OPTIONS=--max-old-space-size=16384

However the actual running process is:

ps -fp $(pgrep -fn lodestar)

showing:

/tmp/caxa/applications/lodestar/.../node --max-old-space-size=8192 ...

During catch-up sync the client consistently crashes around ~8 GB heap usage with:

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

This suggests the packaged launcher is forcing an 8192 MB heap limit internally and preventing operators from overriding it.

### Expected behavior

able to catch-up sync without crashing

### Steps to reproduce

_No response_

### Additional context

_No response_

### Operating system

Linux

### Lodestar version or commit hash

Lodestar/v1.42.0/443e0a4

Start by inspecting the packaged launcher used by /usr/local/bin/lodestar and the /tmp/caxa/applications/lodestar/.../node command; compare its heap flags with NODE_OPTIONS during catch-up sync. Done means the packaged binary honors the configured heap size instead of enforcing 8192 MB and no longer exits at that heap limit.

Written by the indexing model from the issue text.