fix: stop silently swallowing exceptions in indexer search methods

[RicherTunes]

Summary

• SearchAlbumsAsync, SearchTracksInternalAsync, GetAlbumDetailsInternalAsync, and SearchEnhancedAsync previously caught exceptions, reported them via bridge reporters, then returned empty results ([] or a default StreamingAlbum). This silently hid API failures, auth errors, and rate limits from callers -- Lidarr would show zero results with no indication anything went wrong.
• All four methods now rethrow after reporting through IIndexerStatusReporter, so callers (Lidarr) can surface errors to users and apply retry logic.
• GetAlbumDetailsInternalAsync also gains IIndexerStatusReporter.ReportErrorAsync calls in its catch block (previously it only logged) and SearchEnhancedAsync gains the same reporter integration for consistency.
• The happy path is completely unchanged. Bridge reporter calls are preserved.
• The null-mapping fallback in GetAlbumDetailsInternalAsync is moved inside the try block since it is only needed when the API call succeeds but mapping returns null -- it should not mask exceptions.

Test plan

• All 649 tests pass (0 new failures introduced; 61 pre-existing HostBridge FV 9.0 assembly failures identical to main)
• No existing tests assert empty-result-on-error for the changed methods
• Verify Lidarr surfaces indexer errors in the UI when Tidal API is unreachable
• Verify rate limit errors from Tidal propagate to Lidarr's retry logic

🤖 Generated with Claude Code