`ComponentColumnDescriptor::is_static` and other metadata flags can be wrong
Given a single chunk, it's impossible to know if a column is truly static, or semantically empty. That can only be determined by considering the entire set of chunks comprising a store/recording/partition. Our current implementation of ComponentColumnDescriptor does NOT reflect this. As a result, it's is_static field (and other metadata flag) can be wrong, depending on how the schema was computed.
ChunkBatch::chunk_schema()-> WRONG (potentially)- `ChunkStore::schema() -> correct
re_chunk_store::SchemaBuilder()-> correct
This discrepancy should absolutely be captured by our type system by either:
- not having those flag at all when getting a chunk's schema
- having those flag, but clearly identified as "chunk-level" (as opposed to "store-level")
Similar to this issue, a chunk's column being is_sorted is no indication that the recording/partition it belongs to has this column actually sorted. As a result, the is_shorted metadata should be dropped each time metadata is aggregated.