Preserve timezone in arithmetic operations on DateTime

[alexey-milovidov]

Changelog category (leave one):

• Bug Fix

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Fixed the issue: timezone was not preserved if you write a simple arithmetic expression like time + 1 (in contrast to an expression like time + INTERVAL 1 SECOND). This fixes #5743

[alexey-milovidov]

Performance test is failed, need to fix.

[alexey-milovidov]

Still have some issues: https://clickhouse-test-reports.s3.yandex.net/9323/61815d8684f78b813a1b5ada01604a19bb893d78/performance_test/comparison_max_rps_gcc_9.html

[alexey-milovidov]

Still need to fix two queries in perf test.

[alexey-milovidov]

The code is absolutely the same but this PR is up to 10% worse:

SELECT count() FROM system.numbers WHERE NOT ignore(toDateTime('2017-01-01 00:00:00') + number)

Bad: 855.21 million rows/s.

AddSecondsImpl constant_vector

 14.85 │50:   movdqu (%rdx,%rax,2),%xmm0
 46.97 │      movdqu 0x10(%rdx,%rax,2),%xmm2
 10.61 │      shufps $0x88,%xmm2,%xmm0
  7.88 │      paddd  %xmm1,%xmm0
 19.70 │      movups %xmm0,(%rsi,%rax,1)

Good: 933.69 million rows/s.

BinaryOperationImplBase constant_vector

 17.81 │28:   movdqu (%rsi,%rax,2),%xmm0
 44.89 │      movdqu 0x10(%rsi,%rax,2),%xmm2
 11.88 │      shufps $0x88,%xmm2,%xmm0
  6.89 │      paddd  %xmm1,%xmm0
 18.53 │      movups %xmm0,(%rdx,%rax,1)

[alexey-milovidov]

The code is absolutely the same but this PR is up to 10% worse

I decided that it's bearable.