Obfuscate IDs in Creator Node stream route

[piazzatron]

Testing

• successfully stream track: spun up all services locally, uploaded song via dapp, searched for it in V1 API, followed redirect to CN, streamed in browser
• curl http://localhost:4000/tracks/stream/1 -I -H "Range: bytes=0-1023" # returned 216
• curl http://localhost:4000/tracks/stream/1 -I -H "Range: bytes=0-1019285719827" # returned 416
• curl http://localhost:4000/tracks/stream/1 -I # returned 200

Additional Notes

• This also fixed a previously unknown bug where we didn't wrap this endpoint handleResponse, causes it to stall forever rather than returning non-200 responses.

[dmanjunath]

Looks good to me. I also want to get @SidSethi or @hareeshnagaraj's eyes on this cause it involves the gateway api route

[dmanjunath]

Don't know if you saw already, but looks like there's some lint errors @piazzatron

[SidSethi]

looks good from my view. per offline discussion, lets just flesh out the PR description with your local QA testing checklist + some code comments clarifying the handleResponse / stream weirdness

also unit test per today's process change 🙂

[SidSethi]

thanks for adding the docs + test 🙂