[Before forward-ports] Antalya 26.3: patch for SettingsChangesHistory

[zvonand]

When porting to future Antalya versions:

• generate .tsv file containing settings values in latest Antalya release (more details in comments in tests/queries/0_stateless/02995_new_settings_history.sh), change the version number in test accordingly;
• add new version section for the next release in src/Core/SettingsChangesHistory.cpp;

When cherry-pinking, do cherry-pick -n avoid picking:

• ...tsv file: it needs to be re-generated
• SettingsChangesHistory.cpp: instead, take Antalya-related sections from previous Antalya release's SettingsChangesHistory.cpp and manually add them to current file. comment all lines with Antalya-specific settings.

Changelog category (leave one):

• Not for changelog (changelog entry is not required)

CI/CD Options

Exclude tests:

• Fast test
• Integration Tests
• Stateless tests
• Stateful tests
• Performance tests
• All with ASAN
• All with TSAN
• All with MSAN
• All with UBSAN
• All with Coverage
• All with Aarch64
• All Regression
• Disable CI Cache

Regression jobs to run:

• Fast suites (mostly <1h)
• Aggregate Functions (2h)
• Alter (1.5h)
• Benchmark (30m)
• ClickHouse Keeper (1h)
• Iceberg (2h)
• LDAP (1h)
• Parquet (1.5h)
• RBAC (1.5h)
• SSL Server (1h)
• S3 (2h)
• S3 Export (2h)
• Swarms (30m)
• Tiered Storage (2h)

[github-actions]

Workflow [PR], commit [9633607]

[ianton-ru]

test_backward_compatibility/test_convert_ordinary.py::test_convert_ordinary_to_atomic broken, fix in #1646 - 24b139f

[ianton-ru]

Regression tests failed because test unmerged features, ignore it.

[ianton-ru]

Does this line correct before feature with object_storage_cluster merged? (Same for all Antalya-only features)

[zvonand]

I guess so. A setting in CH is compared against this file, not the other way around. So it is fine to have some unincluded extra.