Timestamps having different timezone cannot be represented in the same field of a schema

### Is your feature request related to a problem or challenge?

We should be able to handle the cases where timestamps with different timezone data are stored in the same field of a schema. However, `Field` struct holds a `DataType` info, and if we want to place a different timezone:
`ArrowError(InvalidArgumentError("column types must match schema types, expected Timestamp(Millisecond, Some(\"+03:00\")) but found Timestamp(Millisecond, None) at column index 0"))`

### Describe the solution you'd like

Timezone check for timestamps can be ignored while matching columns with the schema

### Describe alternatives you've considered

-

### Additional context

-

Start by locating the schema column-matching logic that compares Timestamp timezone metadata and read the surrounding tests. Reproduce the reported mismatch between Some("+03:00") and None, then verify that columns differing only in timezone metadata are accepted without allowing unrelated type differences.

Written by the indexing model from the issue text.