...

The reason to keep `consumed` is that in the table() API, the reason we could omit `consumed` or `materialized` is that they could share the `keySerde` and `valueSerde` during state store and node construction. This in the windowed table context, however, is not true, since we are using both windowed keySerde and raw keySerde at the same time. So both structs are required.

One side effect is that we bring `ChangeLoggingWindowBytesStore` public for unit test purpose.

Compatibility, Deprecation, and Migration Plan

...