fix: handle Sentry issue for CSV downloading errors

[bolinocroustibat]

Attempt to handle numerous Sentry errors similar to #145755 in a more explicit and generic way:

• Catch the exception when the CSV URL is not reachable and rename it more clearly, so that it can be more instantaneously understood as non major when browsing Sentry
• New custom IOException using a new parent class ExceptionWithSentryDetails which sends details to Sentry as tags, also inherited by the recent custom ParseException
• Move the errors.py file from /analysis to /utils, since it's more broadly used throughout the code
• Use sentry_sdk.Hub.current.client instead of config.SENTRY_DSN to check if Sentry is correctly working, as it is the recommended way

[maudetes]

I think if we raise an error, we won't return the tmp_file and maybe won't remove it in the finally close?

[maudetes]

I don't think this makes the error more explicit than previously?
I think the issue is more about marking these as "expected" in sentry

[bolinocroustibat]

I think the error is more explicit that way, at least it does describe it in the title. For now in Sentry it's not easy to identify what is the issue is when listing the errors, and that way we can see immediately in list mode that it's an "expected" error.

We could also create a specific exception for this, which would include attributes to identify the ressource, as we did for the custom ParseException. What do you think?

[bolinocroustibat]

We could also create a specific exception for this, which would include attributes to identify the ressource, as we did for the custom ParseException. What do you think?

Update: it has been done in this PR, as a proposal. Please review again!

[bolinocroustibat]

I think if we raise an error, we won't return the tmp_file and maybe won't remove it in the finally close?

Good point, thanks. Logic has been modified since then, try/catch block now has a finally block to close and return the temp file.