Read and manage a TIDAL user's playlists and collection via the TIDAL API using authorization-code user auth

Steps

1. Implement the OAuth 2.0 Authorization Code flow with PKCE (or use a TIDAL SDK's init/initializeLogin/finalizeLogin helpers) to get a user-context access token with the necessary scopes
2. Call the user playlist endpoints (documented under the TIDAL Web API reference, e.g. the user-playlist resource) to list a user's own playlists
3. Fetch 'my collection' style resources for the authenticated user to read their saved tracks/albums/artists, using the same bearer token
4. For write operations (creating a playlist, adding/removing tracks), consult the current API reference for the specific playlist-mutation endpoints and required JSON:API request body shape, since TIDAL has been incrementally rolling out full playlist manipulation beyond read access
5. Always pass `countryCode` and use the `include` parameter to expand relationships (e.g. tracks, artists) in a single request rather than making N+1 calls
6. Refresh or re-derive the access token via the SDK's credentials provider rather than storing a single long-lived token, to handle silent token upgrades