MWL no longer requires customers to configure specific time/space aggrs

[api-clients-generation-pipeline]

See DataDog/datadog-api-spec#3749
Test branch datadog-api-spec/test/chuck.hagenbuch/remove-aggregation-parameters-for-mwl

[datadog-datadog-prod-us1]

Datadog Report

Branch report: datadog-api-spec/generated/3749
Commit report: 9b285f9
Test service: datadog-api-client-ruby

❌ 2 Failed (0 Known Flaky), 86 Passed, 2012 Skipped, 25.83s Total duration (47.28s time saved)

❌ Failed Tests (2)

• Tag Configuration Cardinality Estimator returns "Success" response - Metrics at features/v2/metrics.feature

• Tag Configuration Cardinality Estimator returns "Success" response - Metrics at features/v2/metrics.feature - Details

  Expand for error

   There are unused HTTP interactions left in the cassette:
     - [get https://api.datadoghq.com/api/v2/metrics/system.cpu.idle/estimate?filter%5Bgroups%5D=app%2Chost&filter%5Bnum_aggregations%5D=4] => [200 "{\"data\":{\"attributes\":{\"estimated_output_series\":68,\"estimate_type\":\"count_or_ga"]