Extend index tables' partitioning settings to be able to restore them from a backup with the same partitioning as before

[jepett0]

#4955

There are 3 major commits in this PR, whose purposes are the following:

• 90162f5 Extend ydb_table.proto to be able to specify partitioning settings of the indexImplTable and explicit partition boundaries (or uniform partition count) of the index table at the moment of its creation. There is also a functional test using GRPC calls that shows that it becomes possible to create a table with extended index partitioning settings.
• c96c24f Changes in cpp SDK to be able to describe extended partitioning settings and explicit partition boundaries (if any) of secondary indexes of the table. This is necessary to be able to dump and restore the table with the extended index partitioning info.
• 49321ec Unit tests and functional tests of the feature.

Note: each major commit is preceded by a minor refactoring change. For the best reviewing experience, please review these changes separately.

[jepett0]

There is a direct leak in one of the added unit tests. However, it is not a new problem. It can be reproduced on a YDB cluster that uses ydbd binary that was built with --sanitize=leak flag by exporting to S3 and then importing back and stopping the server.

I propose to fix the leak in an other PR. I have created a ticket to track the issue.

[github-actions]

⚪ 2024-06-21 12:12:36 UTC Pre-commit check for 112511b has started.
⚪ 2024-06-21 12:16:08 UTC Build linux-x86_64-release-asan is running...
🟢 2024-06-21 12:47:08 UTC Build successful.
⚪ 2024-06-21 12:47:21 UTC Tests are running...
🔴 2024-06-21 15:01:55 UTC Some tests failed, follow the links below.

Test history | Test log

TESTS	PASSED	ERRORS	FAILED	SKIPPED	MUTED?
15500	14868	0	101	360	171

🟡 2024-06-21 15:02:42 UTC ydbd size 5.5 GiB changed* by +423.0 KiB, which is >= 100.0 KiB vs main: Warning

ydbd size dash	main: e61d9af	merge: 112511b	diff	diff %
ydbd size	5 854 489 424 Bytes	5 854 922 608 Bytes	+423.0 KiB	+0.007%
ydbd stripped size	1 255 507 080 Bytes	1 255 576 776 Bytes	+68.1 KiB	+0.006%

^{*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation}

[github-actions]

⚪ 2024-06-21 12:19:30 UTC Pre-commit check for 112511b has started.
⚪ 2024-06-21 12:23:09 UTC Build linux-x86_64-relwithdebinfo is running...
🟢 2024-06-21 12:55:37 UTC Build successful.
⚪ 2024-06-21 12:55:47 UTC Tests are running...
🔴 2024-06-21 15:34:26 UTC Some tests failed, follow the links below.

Test history | Test log

TESTS	PASSED	ERRORS	FAILED	SKIPPED	MUTED?
76212	62892	0	5	13305	10

🟡 2024-06-21 15:35:13 UTC ydbd size 8.3 GiB changed* by +656.3 KiB, which is >= 100.0 KiB vs main: Warning

ydbd size dash	main: 247b6a0	merge: 112511b	diff	diff %
ydbd size	8 960 488 848 Bytes	8 961 160 856 Bytes	+656.3 KiB	+0.007%
ydbd stripped size	488 356 264 Bytes	488 377 704 Bytes	+20.9 KiB	+0.004%

^{*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation}

[github-actions]

⚪ 2024-06-21 12:31:21 UTC Pre-commit check for 112511b has started.
⚪ 2024-06-21 12:34:59 UTC Build linux-x86_64-release-clang14 is running...
🟢 2024-06-21 13:15:06 UTC Build successful.

[jepett0]

There is a direct leak in one of the added unit tests. However, it is not a new problem. It can be reproduced on a YDB cluster that uses ydbd binary that was built with --sanitize=leak flag by exporting to S3 and then importing back and stopping the server.

I propose to fix the leak in an other PR. I have created a ticket to track the issue.

I decided to remove this test from the PR. I will add it back after I fix the problem with the leak