The following aggregations don't work well with `time_series` aggregation:

- `sampler`
- `composite`

Any aggregation that returns a `LeafBucketCollector.NO_OP_COLLECTOR` instance as leaf collector.

Also the filter by filter optimisation that a number of aggregations perform doesn't work when executing in time series mode.
#91702 already disables this optimisation in case `time_series` agg is used. We should do that also for the mentioned aggregations.

Separately we should also investigate how to make these aggregations and filter by filter optimisation work with `TimeSeriesIndexSearcher`.
server/src/main/java/org/elasticsearch/search/aggregations/bucket/composite/CompositeAggregationBuilder.java
return this;
    }
    /**
     * The number of composite buckets to return. Defaults to {@code 10}.
     */
    public CompositeAggregationBuilder size(int size) {
        this.size = size;
        return this;
    }
    /**
     * @return the number of composite buckets. Defaults to {@code 10}.
     */
    public int size() {
        return size;
    }
    @Override
    public BucketCardinality bucketCardinality() {
        /*
         * Cardinality *does* have buckets so MULTI might be appropriate here.
         * But the buckets can't be used with the composite agg so we're
         * going to pretend that it doesn't have buckets.
         */
        return BucketCardinality.NONE;
    }
    /**
     * Returns null if the provided factory and his parents are compatible with
     * this aggregator or the instance of the parent's factory that is incompatible with
     * the composite aggregation.
     */
    private static AggregatorFactory validateParentAggregations(AggregatorFactory factory) {