[Feature Request] Store third-party identifiers

[FoxxMD]

Implement storage of 3rd party IDs for tracks, artists, and albums. Common IDs:

• Musicbrainz MBID
• Spotify URI/ID

Benefits of storage:

• Makes album/artist artwork lookup require less api calls
• Can serve "external links" for spotify directly instead of using search
• Enables easier duplicate detection
• Enables easier re-parsing and metadata lookup in the future

The IDs could be stored on a new table that is a simple KV store with a FK/discriminator for the entity it is associated with. The ID should be able to be submitted alongside a new scrobble (free lookup!) since some scrobble clients can do this. Additionally, it should be able to be edited/updated through an API endpoint.

[nemethf]

Since commit 1eaba888c741c7af1d5a5e772e70cb2277be3d1a, maloja saves various MBID tags

[FoxxMD]

say whaaat. It looks like this is just for the listenbrainz endpoint, however. The native endpoint does not store extra fields and the scrobbles endpoint does not display them.

[duckfromdiscord]

We could add something like extrafields https://github.com/krateng/maloja/commit/1eaba888c741c7af1d5a5e772e70cb2277be3d1a#diff-ec004ea2624df9dbf01f0e52f82d9c78355e56aa9a3a0dd73f372ed4c10f0d77R70 to the maloja api? Assuming self.scrobble stores those **extrafields?

[duckfromdiscord]

Would be cool to store spotify data too for cases like mine where I scrobble from spotify but have not used it to gather album art data yet and would like to later on

[duckfromdiscord]

361 would fix this issue