Use setters in IO options builders instead of directly modifying the data members

[vuule]

Description

Route IO builders through option setters because they are responsible for validation.
Also fixed validation in set_quoting.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[coderabbitai]

📝 Walkthrough

Walkthrough

Changes

IO option builder updates

Layer / File(s)	Summary
CSV option setters and builders cpp/include/cudf/io/csv.hpp	CSV reader and writer builders now use public setter APIs, with move forwarding for transferred values. Prefix assignment is move-based, and quoting validation accepts an expanded set of styles.
Avro and JSON builder forwarding cpp/include/cudf/io/avro.hpp, cpp/include/cudf/io/json.hpp	Avro and JSON reader and writer builders now forward configuration through corresponding setter and enable methods.
ORC reader setter and builder integration cpp/include/cudf/io/orc.hpp	ORC adds the timezone-ignore setter and routes reader builder updates through public APIs.
ORC writer builder forwarding cpp/include/cudf/io/orc.hpp	ORC writer and chunked writer builders now use public setters for writer configuration.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Suggested labels: cuIO

Suggested reviewers: davidwendt

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly summarizes the main change: routing IO option builders through setters instead of direct member access.
Description check	✅ Passed	The description matches the changeset and correctly mentions using option setters and fixing quoting validation.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[davidwendt]

Just want to point out that because these functions are coded in header files, all files that include them now need to be recompiled. If the definitions were moved to .cpp files then changing internal implementation details like this would only require those cpp files to be recompiled.

[vuule]

Just want to point out that because these functions are coded in header files, all files that include them now need to be recompiled. If the definitions were moved to .cpp files then changing internal implementation details like this would only require those cpp files to be recompiled.

Yeah, we can move the definitions into a cpp file (functions.cpp?).

[vuule]

/merge