Support opaque id routes

[raymondjacobson]

Trello Card Link

https://trello.com/c/5Y8RA0Vm/1497-api-expose-audius-client-track-route-to-handle-opaque-ids

Description

There's currently no way to go from API result => audius link. This PR adds support for

/tracks/{hashid}
/users/{hashid}
/playlists/{hashid}

Dragons

Is there anything the reviewer should be on the lookout for? Are there any dangerous changes?

This touches page load for tracks, users, and playlists which is a BFD. I tried to be very thorough in testing and I will continue to do so, but extra care in review would be great.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide repro instructions & any configuration.

New unit tests as well as manual testing (local pointed @staging):

tracks
/tracks/DOg1D

• load track page with normal track route
• load track page with hashed track route
• set a remix of a track
• load track page with normal track route and view remixes
• load track page with hashed track route and view remixes
• load track page that should 404 (/handle/track-asdf)
• load a track page that should 404 (/tracks/invalid)
• rename a track
• for an unlisted track, ensure that it 404s if trying to reach it by its hashed id
• for an unlisted track, ensure that it 404s if trying to reach it by the correct id but incorrect track name/route id

users
/users/5epYn

• load user page with normal handle route
• load user page with hashed id route

playlists
/playlists/naZEL

• load playlist page with normal playlist route
• load playlist page with hashed playlist route
• load album page with normal album route
• load album page with hashed playlist route
• create playlist and wait for confirmation
• create playlist and leave before confirmation
• rename playlist

misc

• upload a track & visit page immediately

[audius-infra]

Preview this change https://frontend-demo.audius.co/rj-opaque-id-routes

[raymondjacobson]

Note two bugs i'm still working out that i've caught w/ testing

• profile page => other base route causes page breaking
• mobile track page other artist tracks not loading

will fix these before merge. PR otherwise should be fine to review from a code persp.

[piazzatron]

Looks great - didn't find any issues with it in my testing. Besides the code level comments, the only other thing I can think that we need to do are block the playlists/tracks/users handles. Some fairly inactive user already grabbed playlists unfortunately, but what can you do (I guess we could call it collections?).

One more thing to test - does this all work with the app-redirect system? I'm not sure why it would cause that to break, but worth testing.