[MPDX-8418] Add UTF-8 BOM to CSV exports

[canac]

Description

Excel does not interpret UTF-8 encoded CSV files correctly. For example, exports contain characters like this instead of Russian characters: "–ï–¥–∞/–ø–æ–¥–∞—Ä–∫–∏ –¥–ª—è –≤—Å—Ç—Ä–µ—á –£–∂–∏–Ω –° –∫–æ–º–∞–Ω–¥–æ–π –∏ —Å —Å—Ç—É–¥–µ–Ω—Ç–∞–º–∏". To fix this, we need to add the Byte Order Mark to hint to Excel that it needs to interpret the file as UTF-8 instead of as ASCII. Fortunately, react-csv has an option for this. We just have to pass true as the second argument to buildURI.

I also migrated the account transactions CSV download from a handrolled CSV export to use react-csv.

Note that the API already adds the byte order mark to server-generated CSV exports.

Testing

• 14 Month Reports
  • Create or edit a contact to have a non-ASCII character in its name, like Á.
  • Go to a 14 month report and export it
  • Check in Excel (if available) and macOS Numbers that the CSV file is rendered correctly
  • Alternatively, open the CSV file in VS Code and check that it says "UTF-8 with BOM" in the status bar at the bottom of the window
• Transactions Report
  • Impersonate Toncho's account
  • Go to a responsibility centers transactions page with transactions (I had to push the start date back to see transactions)
  • Click Export CSV button
  • Check in Excel (if available) and macOS Numbers that the CSV file is rendered correctly
  • Alternatively, open the CSV file in VS Code and check that it says "UTF-8 with BOM" in the status bar at the bottom of the window

MPDX-8418

Checklist:

• I have given my PR a title with the format "MPDX-(JIRA#) (summary sentence max 80 chars)"
• I have applied the appropriate labels. (Add the label "On Staging" to get the branch automatically merged into staging.)
• I have requested a review from another person on the project

[github-actions]

Preview branch generated at https://8418-csv-utf8.d3dytjb8adxkk5.amplifyapp.com

[github-actions]

Bundle sizes [mpdx-react]

Compared against 758815f

No significant changes found

[dr-bizz]

Looks great!

[dr-bizz]

Its a shame we are losing testing what the href will actually look like, but it makes sense to just mock the buildURI.

[canac]

I think it's actually a good thing that the component unit test isn't concerning itself with CSV formatting and that we're trusting the react-csv to build a valid URL. If we don't trust the library's test coverage or functionality, we could write our own unit tests to directly test buildURI.