Backport MPD manifest parsing fixes from main repo

[YutongGu]

fix(playback): Avoid MPD manifest parsing to fix regression with new TIDAL group="main" manifests

TIDAL appears to have changed the MPEG-DASH MPD manifests returned for some streams to include non-numeric values in
<AdaptationSet group="..."> (e.g. group="main").

The current mpegdash parser expects group to be an integer and raises a ValueError, which tidalapi wraps as ManifestDecodeError. This caused mopidy-tidal playback to fail and tracks to be marked “not playable”.

This PR updates mopidy-tidal’s playback provider to avoid parsing MPD manifests via tidalapi/mpegdash.

For MPD manifests we only need to persist the MPD XML and return a file:// URI, so parsing is unnecessary.

Root cause

• tidalapi.StreamManifest → DashInfo.from_mpd() → mpegdash parser

• New MPD contains: <AdaptationSet ... group="main" ...>

• mpegdash tries to parse group as int → ValueError → tidalapi.exceptions.ManifestDecodeError

• Mopidy logs: backend exception + Track is not playable

Changes

• MPD path (ManifestMimeType.MPD)
  • Stop calling stream.get_stream_manifest() (this triggers MPD parsing and the crash)
  • Use stream.get_manifest_data() to fetch raw MPD XML
  • Write the MPD to manifest.mpd in the extension cache directory
  • Return file://…/manifest.mpd for playback (same end result as before, but without parsing)
• BTS path (ManifestMimeType.BTS)
  • Keep existing behavior using stream.get_stream_manifest()

Why this is safe

mopidy-tidal already ultimately plays MPD by writing it to disk and handing Mopidy a file:// URI.

The parsed MPD data from tidalapi wasn’t required for playback logic here; it was effectively only used for logging (codecs).