Catch ZstdError in jlap/repodata.json.zst handling

[dholth]

Description

Fix #13558

Checklist - did you ...

• Add a file to the news directory (using the template) for the next release's release notes?
• Add / update necessary tests?
• Add / update outdated documentation?

[codspeed-hq]

CodSpeed Performance Report

Merging #13559 will create unknown performance changes

_{Comparing 13558-repodata-zst-fallback (5518720) with main (b60f12b)}

Summary

⚠️ No benchmarks were detected in both the base of the PR and the PR.

[jezdez]

I think that's reasonable, so maybe sanitize it? Or leave out the URL?

[dholth]

Improved.

[jezdez]

Not sure if we actually need the debugging statement, but I concur it's good to catch zstandard decompression exceptions

[dholth]

In general this entire code path could be more clear about whether the user's web server is configured correctly, and which variant they wind up getting. If we don't say something then the user would not know that they have a "404 page that returns a 200 code" for repodata.json.zst

For the unchanged code possibly more HTTP errors should result in "use repodata.json and don't check repodata.json.zst for another week"

[jezdez]

Then lets make this and the other possible cases result in more specific (and actionable) logging statement? Info level?

[dholth]

Improved log message with sanitized URL, and a bonus sanitized URL in a similar log message.