sql: support cvs format options in copy-to-s3

[maddyblue]

These were being silently ignored.

Motivation

• This PR fixes a previously unreported bug.

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• This PR includes the following user-facing behavior changes:
  • n/a

[maddyblue]

@rjobanp Saw this when looking at some code. I didn't see a test that asserted file contents of the uploaded s3 files, so that should be added here before merging. Are you or someone from testing able to take that over?

[rjobanp]

thanks for implementing this!

[rjobanp]

I didn't see a test that asserted file contents of the uploaded s3 files

Sorry just saw this comment! We do assert the contents of files in this test https://github.com/MaterializeInc/materialize/blob/main/test/testdrive/copy-to-s3-minio.td#L145-L158

I'll update this PR to validate that these format options also affect the CSV output format there