Disable activity log for self managed

[SangJunBak]

Was able to test this by using bin/mzimage acquire orchestratord to get a new image then pointing the helm chart at it

Motivation

Fixes https://github.com/MaterializeInc/cloud/issues/10755

Dependent on https://github.com/MaterializeInc/console/pull/3683 being merged and the tag being pushed

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.

[SangJunBak]

@jubrad Figured you'd be the best person to review this since it seems like versioning is top of mind! Added you to the Console equivalent PR too https://github.com/MaterializeInc/console/pull/3683. Some questions:

• Given I updated deployment.yaml, do I need to update the helm chart version?
• In this commit, the tag is set to v0.133.0-dev.0 for orchestratord. When we backport, is the plan to update this value in values.yaml accordingly?
• On the Console end, instead of backporting the change in the PR, I was just going to fast forward the LTS branch to current main given they're both backwards compatible with each other then pushing 25.1.0-beta.4 to dockerhub. Is that ok?

[SangJunBak]

Emulator has statement logging disabled by default already