Fix naming collisions in obolup - follow naming convention

[bussyjd]

Problem

Running obolup multiple times causes StatefulSet naming collisions:

Error: UPGRADE FAILED: failed to replace object: StatefulSet.apps "l1-light-client-helios" is invalid:
spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'ordinals', 'template',
'updateStrategy', 'revisionHistoryLimit', 'persistentVolumeClaimRetentionPolicy' and 'minReadySeconds' are forbidden

Root Cause

• Hardcoded release name l1-light-client (line 512 in obolup/obolup)
• No network identifier in resource names
• No collision detection or graceful handling

Solution

1. Follow the naming convention: l1-{client}-{network}-{component}
2. Handle collisions gracefully (skip with warning or respect --clean flag)

Example fix:

# Change from:
helm upgrade --install l1-light-client obol/helios ...

# To:
helm upgrade --install l1-helios-$__network obol/helios ...

This creates network-specific resources like l1-helios-mainnet-light instead of colliding l1-light-client-helios.