Update Kafka Progress Topic config to avoid long startups

[patrickwwbutler]

Updates the segment.bytes config value to 128MiB to avoid having to process large amounts of progress data when creating new sinks.

Motivation

• This PR adds a known-desirable feature.

https://github.com/MaterializeInc/database-issues/issues/9894

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.

[martykulma]

Nice, thanks @patrickwwbutler !

There's also a section for the progress topic in the docs that could use a mention of the segment size: https://materialize.com/docs/serve-results/sink/kafka/#automatic-topic-creation

[DAlperin]

LGTM! Thank you!

[martykulma]

🐟