Feature Request: Detailed csv errors

[surfaceflinger]

Describe the feature

Show on which line+column the csv parser failed during imports.
Maybe a snippet of our csv could be displayed and the wrong part be colored in red?

Why is this feature important?

When exporting csv from banks we can pretty much expect to see one of the weirdest csvs in our lifes, at least that's the case with polish branch of ING.

After removing all of the unnecessary stuff from my export and leaving only transactions in, the only thing Maybe shows is "Must be valid CSV with headers and at least one row of data". This forces me to pretty much start bisecting the csv instead of instantly going to the right field and checking what caused this.

Additional context, screenshots, and relevant links

Checked if someone else came up with this and found only this: #1309 pretty sure this user either wouldn't have a problem or would describe a case where the csv parser could be improved(?)

[zachgoll]

@surfaceflinger I think you might need to update your app to the latest version. We have all of this live:

[surfaceflinger]

Huh, when was this added? I've setup my instance from main like a week ago, but I can see that "Error rows" string was in code at least since 398b246 🤔

Unless the problem with my csv is even worse, will try to check it with some linters instead later

[zachgoll]

This was added several months ago. If you're not seeing this UI, then there may be a bug caused by something else that we need to dig into.