Enable CSVParser to handle CSV files in UTF-8 with or without a BOM

Currently, if a manifest CSV file has a BOM, this gets parsed as the first character of the file, and thus the first character of the first header, resulting in an error when the headers are checked for validity. Since the BOM is a non-printing character, this is difficult to diagnose and fix.

This merge request allows the CSV parser to silently handle files with the correct BOM for their encoding.