Fix Timestamp to align with ORC spec

[Jefffrey]

ORC timestamp type is not straightforward, as though it apparently represents a timestamp without a timezone, its encoding & decoding is still dependent on the writer timezone (encoded in the stripe) and the reader timezone.

This is why the 1900 & 2038 integration tests are currently disabled as our implementation is incorrect:

datafusion-orc/tests/integration/main.rs

Lines 155 to 165 in 3369b5d

	#[test]
	#[ignore] // TODO: Incorrect timezone + representation differs
	fn test_date_1900() {
	test_expected_file("TestOrcFile.testDate1900");
	}
	#[test]
	#[ignore] // TODO: Incorrect timezone + representation differs
	fn test_date_2038() {
	test_expected_file("TestOrcFile.testDate2038");
	}

[Jefffrey]

FYI I've raised a PR to update ORC spec for timestamp: apache/orc#1867

Since that was what caused initial confusion for me, as some key implementation details were not mentioned in the spec leading to the initial inaccurate implementation

Also worth noting how arrow deals with this:

https://github.com/apache/arrow/blob/24feab091ab5a05b1cec234f51bd0223e2c41487/cpp/src/arrow/adapters/orc/adapter.cc#L178-L181

apache/arrow#34590

[Jefffrey]

Note that the 2038 test is dependent on chronotope/chrono-tz#155 as it tests timestamps 2100 and beyond, which chrono_tz currently has inaccurate DST for

Edit: chronotope/chrono-tz#135

[Jefffrey]

Partially resolved by 60288cd

Still pending chrono_tz fix for large date DST