Add timezone offset for debug format of Timestamp with Timezone

[waitingkuo]

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

fn main() {
    let arr = TimestampSecondArray::from_vec(vec![0], Some("America/New_York".to_string()));
    println!("{:?}", a);
}

this outputs followings for now

PrimitiveArray<Timestamp(Second, None)>
[
  1970-01-01 00:00:00,
]

Describe the solution you'd like

outputs something like this

PrimitiveArray<Timestamp(Second, Some("America/New_York"))>
[
  1969-12-31 19:00:00 -05:00,
]

Describe alternatives you've considered

Additional context

we could extends

arrow-rs/arrow-array/src/array/primitive_array.rs

Lines 554 to 560 in 22e742b

	DataType::Timestamp(_, _) => {
	let v = self.value(index).to_isize().unwrap() as i64;
	match as_datetime::<T>(v) {
	Some(datetime) => write!(f, "{:?}", datetime),
	None => write!(f, "null"),
	}
	}

by as_datetime_with_timezone which will be added in #2909

[waitingkuo]

@tustvold @jhorstmann do you think we should show
1970-01-01T00:00:00 or
1969-12-31T19:00:00-05:00
in this case?

in prettyprint i prefer the one with timezone shift. but for the Debug, should we just show the underline datetime without the offset shift?

[tustvold]

My vote would be for consistently outputting RFC3339

[waitingkuo]

if timezone is incorrect, say "Asia/Taipei2", should we output something like this?

+--------------------------------------------------------+
| Timestamp(Second, Some("Asia/Taipei2")) |
+--------------------------------------------------------+
| 1970-01-01T00:00:00 (Unknown Time Zone 'Asia/Taipei2') |
+--------------------------------------------------------+

note that this the prettyprint's result in #2939

[alamb]

label_issue.py automatically added labels {'arrow'} from #3072