BREAKING: Use BOM-less UTF-8 encoding for writes, #1027

[paulirwin]

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a change, please open an issue to discuss the change or find an existing issue.

Use BOM-less UTF-8 encoding for writes

Fixes #1027

Description

See #1027 for details.

[paulirwin]

@NightOwl888 I assume this comment on the issue was really for this PR instead: #1027 (comment)

I went ahead and took option 1 to remove the field, and renamed CHARSET_UTF_8 as you noted as well. For consistency with use elsewhere and in Lucene, I left an underscore between "UTF" and "8" as ENCODING_UTF_8_NO_BOM.