fix: update Spotify extended streaming history schema to match new format

[mroetsc]

Description

Spotify seems to have changed their extended streaming history export format. This PR updates the validation schema to match the new format.
Fixes #452
Solution described in #452 (comment)

Changes

• Updated fullPrivacyFileSchema to match Spotify's new export format:
  • Removed username field (no longer provided)
  • Removed user_agent_decrypted field (no longer provided)
  • Renamed ip_addr_decrypted to ip_addr to match new field name

[DenuxPlays]

@Yooooomi Can this please be merged and released?

[Yooooomi]

Hello there, thanks for the work, can you please provide a ts field that is appearing in the json files? Is the format a number or a string?
Also, I'm getting rid of the unused fields too so that it is lighter.

[n-AChegYag]

Hello there, thanks for the work, can you please provide a ts field that is appearing in the json files? Is the format a number or a string?您好，感谢您的工作，您能提供一个出现在 json 文件中的ts字段吗？格式是数字还是字符串？ Also, I'm getting rid of the unused fields too so that it is lighter.另外，我也去掉了未使用的字段，以便它更轻。

like this:
"ts": "2024-04-18T15:33:22Z"

[DenuxPlays]

Hello there, thanks for the work, can you please provide a ts field that is appearing in the json files? Is the format a number or a string?

Also, I'm getting rid of the unused fields too so that it is lighter.

Will there be a new Release soon?