chore(deps): bump go-openaudio ETL to playlist_contents key fix

[raymondjacobson]

Summary

Bumps go-openaudio and go-openaudio/pkg/etl from 6ea0f10 → 35ad422, picking up go-openaudio#321.

That PR fixes the ETL indexer's playlist_contents JSONB write path: pre-fix it persisted the SDK's track_id / timestamp / metadata_timestamp alias keys verbatim, but every reader on this side only understands the canonical track key —

• api/v1_playlist_tracks query — (e.value->>'track')::int
• the handle_playlist notification trigger — (track_item->>'track')::int
• the dbv1 get_playlists play-count rollup — (e.item->>'track')::int

so affected playlists rendered empty even though the playlist_tracks junction table was correct. After this bump, new writes land in the canonical {track, time, metadata_time} shape.

Backfill

Already-broken is_current rows (65 and climbing at time of writing) are not repaired by this PR — they're fixed by a one-shot SQL backfill run out-of-band. The backfill maps the same alias keys onto the canonical names and was dry-run-verified against prod (2194 entries in → 2194 out, zero drops).

⚠️ Deploy ordering: the backfill should run together with / after this bump deploys. If it ran while the old indexer were still live, new bad rows would keep landing.

Test plan

• go build ./... clean against the bumped deps
• go-openaudio#321 ships the unit tests covering the canonicalization (alias keys, hashid strings, mixed shapes)
• Confirm core-indexer comes up clean post-deploy (stern -n api core-indexer)

🤖 Generated with Claude Code