add test to verify that if default charset is Japanese then for any combination of read/write UTF8 setting all CSV files should be read/write using UTF8
handle all Bulk API files as UTF8 regardless of read/write UTF8 setting and/or system default charset
move MacOS bundle generation to a profile that's only activated on Mac platforms otherwise build fails in Linux
amend previous commit - fix typo
Merge pull request #28 from federecio/develop

When using Bulk API, read/write files in UTF8 regardless of read/write UTF8 setting and system's default charset