Disable the new instrospection sources

[teskje]

This PR disables the two introspection sources added in #29848, because Mz's 0dt mechanism is currently not prepared to handle new introspection sources.

"Disabling" here means removing the registration of the new Log builtins and the Views depending on them. The intention is to keep the diff as small as possible, to make this change less risky.

The plan is to revert this PR once https://github.com/MaterializeInc/database-issues/issues/8731 is resolved.

Motivation

• This PR fixes a recognized bug.

Mitigates https://github.com/MaterializeInc/database-issues/issues/8731 for the release.

Tips for reviewer

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

[def-]

Good for me assuming platform-checks 0dt upgrades in nightly are green: https://buildkite.com/materialize/nightly/builds/10317

[def-]

We are still seeing the logging:

platform-checks-mz_2-1              | cluster-s3-replica-s3-gen-1: 2024-11-08T15:00:40.661245Z  WARN mz_compute::server: halting process: new instance configuration does not match existing instance configuration:

But I think that's actually not a sign of this not working, but instead we already have a v0.124.0 cut that has the problem. So ok from my side.