Disallow ALTERs for Object Storage table engines

[evillique]

Changelog category (leave one):

• Bug Fix (user-visible misbehavior in an official stable release)

Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):

Disallow ALTERs for Object Storage table engines. For example, ALTER ADD PROJECTION could have led to an inability to restart the server, since Object Storage engines do not support projections.

Reference #85769

Documentation entry for user-facing changes

• Documentation is written (mandatory for new features)

[clickhouse-gh]

Workflow [PR], commit [b94cccc]

Summary: ❌

job_name	test_name	status	info	comment
BuzzHouse (amd_debug)		failure
	Logical error: 'Inconsistent AST formatting: the query: (STID: 2508-11b5)	FAIL	cidb

[kssenii]

Disallow ALTERs for Object Storage table engines. For example, ALTER ADD PROJECTION could have led to an inability to restart the server, since Object Storage engines do not support projections.

Why not just disallow alters which include projections? Was there a problem with non-projection alters?
IMO this PR must be marked backward-incompatible at least, and not sure if we allow backporting backward imcompatible changes.

[evillique]

@kssenii Because in the PR I referenced the ALTERs for Object Storage engines were enabled by mistake, without tests for any of them, other than for the DataLakes, which this PR does not touch.

We already disabled ADD_INDEX before that, now we need to disable ADD_PROJECTION, and who knows how many untested ALTERS breaking the production we will need to add.

So if none of them are tested it makes sense to forbid every type of them, essentially returning to the behaviour that was there before that PR.