[Bug]: No transactions detected in bank CSV export

### Verified issue does not already exist?

- [x] I have searched and found no existing issue

### What happened?

When I tried to import the CSV exported from my bank's site, AB says there are no transactions in it:

But if I look into the file, I see that there are 5 transactions in it, and a header row, fields separated by commas.
If I set the "skip start lines" to 1, AB says I cant skip more lines than there is, so maybe it cannot handle the line endings used?

According to the linux "file" command, the is a "Little-endian UTF-16 Unicode text, with very long lines".
I dont know how to tell what line endings it has though, because suprisingly its much harder than on windows.. no text editor I know can tell that to me.

Another problem could be that AB does not allow me to select the standard date format used in my country (YYYY.MM.DD), but that would be on top of the line detection issue. If it turns out to be an issue I'll open a separate issue for that.

### How can we reproduce the issue?

0. You would need a sample export file from my bank
1. Open AB's webapp in Firefox
2. Select an account on the left
3. Click Import at the top
4. Select the sample CSV file

### Where are you hosting Actual?

Docker

### What browsers are you seeing the problem on?

Firefox

### Operating System

Linux

No source file or test is named. Start by reproducing the import in the webapp with the bank's UTF-16 CSV export, then inspect the import handling and verify that the five transactions are detected; the YYYY.MM.DD date format is a separate possible issue.

Scritto dal modello di indicizzazione a partire dal testo della issue.