[feature](type)support timestamptz type (#56646)

[jacktengg]

apache/doris-website#2962

TIMESTAMPTZ implementation does not store time zone information with each row of data, but instead adopts the following mechanism:

1. During storage: All input time values are converted to UTC (Coordinated Universal Time)
2. During query: Based on the session's time zone setting (specified via the time_zone variable), UTC time is automatically converted to the corresponding time zone for display

Therefore, TIMESTAMPTZ can be understood as a DATETIME type with time zone conversion functionality, where Doris automatically handles time zone conversions internally.

None

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:

• This is a refactor/code format and no logic has been changed.
  - [ ] Previous test can cover this change. - [ ] No code files have been changed. - [ ] Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.

• Yes.

• Confirm the release note

• Confirm test cases

• Confirm document

• Add branch pick label

---

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

Release note

None

Check List (For Author)

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:
    • This is a refactor/code format and no logic has been changed.
    • Previous test can cover this change.
    • No code files have been changed.
    • Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.
  • Yes.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label

[Thearas]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?

[jacktengg]

run buildall

[hello-stephen]

Cloud UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	82.10% (1573/1916)
Line Coverage	67.11% (28069/41824)
Region Coverage	67.58% (13803/20426)
Branch Coverage	58.04% (7362/12684)

[hello-stephen]

FE UT Coverage Report

Increment line coverage 19.54% (77/394) 🎉
Increment coverage report
Complete coverage report

[jacktengg]

run buildall

[hello-stephen]

Cloud UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	82.10% (1573/1916)
Line Coverage	67.11% (28068/41824)
Region Coverage	67.63% (13815/20426)
Branch Coverage	58.01% (7358/12684)

[hello-stephen]

FE UT Coverage Report

Increment line coverage 19.54% (77/394) 🎉
Increment coverage report
Complete coverage report

[doris-robot]

BE UT Coverage Report

Increment line coverage 57.24% (692/1209) 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	53.34% (18663/34988)
Line Coverage	39.10% (172830/442002)
Region Coverage	33.77% (133560/395454)
Branch Coverage	34.75% (57743/166148)