KAFKA-19080 The constraint on segment.ms is not enforced at topic level

[m1a2st]

The main reason is that we forgot setting the
TopicConfig.SEGMENT_BYTES_CONFIG at least to 1024 * 1024, thus
addressed it, and add a test for it.

[m1a2st]

Hello @junrao, @chia7712
I have a question about this problem.
In KAFKA-16368, only the ServerLogConfigs value for log.segment.bytes was modified to 1 MB. However, the TopicConfig which in LogConfig default for segment.bytes remains 14 bytes. Many tests rely on this small segment.bytes value to generate a large number of segments.

I think there are two possible approaches to resolve this:

1. Add atLeast(1024 * 1024) validation in LogConfig, which would require fixing around 400 tests.
2. Add a validator in LogManager#updateTopicConfig to validate the change request at runtime.

[junrao]

@m1a2st : Perhaps we could somehow allow the tests to set a small segment.bytes.

[chia7712]

Maybe we can add a internal config to allow tests to define small size?

[chia7712]

for example:

   this.internalSegmentSize = getString(TopicConfig.INTERNAL_SEGMENT_BYTES_CONFIG);

   ...
   
    public long segmentSize() {
        if (internalSegmentSize != null) return Long.parseLong(internalSegmentSize);
        return segmentMs;
    }

[m1a2st]

Thanks for @junrao, @chia7712 comments, This PR is already for review, PTAL.