Enhance arrow-json reader/writer builder pattern to enforce constraints

#6643 introduced new options which affect existing options in the builders.

- Reference: https://github.com/apache/arrow-rs/pull/6643/#pullrequestreview-2564347496

Examples:

```rust
let reader = ReaderBuilder::new(schema)
.with_struct_mode(StructMode::ListOnly)
.with_strict_mode(false) // This has no effect
.build();

let writer = WriterBuilder::new()
.with_struct_mode(StructMode::ListOnly)
.with_explicit_nulls(false) // This has no effect
.build()
```

See if we can utilize Rust's type system to enforce these constraints (e.g. type-state builder pattern). Would likely require a breaking API change.

Start by reviewing PR #6643 and the ReaderBuilder and WriterBuilder APIs described in this issue. Evaluate whether Rust’s type-state builder pattern can enforce the interactions among struct mode, strict mode, and explicit nulls; done means the invalid option combinations are rejected by the API, with any breaking change clearly accounted for.

Written by the indexing model from the issue text.