Rename Datasets to Data Access Controls

[api-clients-generation-pipeline]

See DataDog/datadog-api-spec#5330 Test branch datadog-api-spec/test/dinu.wijetunga/datasets_to_dac_rename

[datadog-datadog-prod-us1-2]

⚠️ Tests

✨ Fix all issues with BitsAI or with Cursor

⚠️ Warnings

🧪 9 Tests failed

Create a Data Access Control dataset returns "Conflict" response from Data Access Controls at features/v2/datasets.feature     (Fix with Cursor)

Cassette '/home/runner/work/datadog-api-client-ruby/datadog-api-client-ruby/cassettes/features/v2/datasets/Create-a-Data-Access-Control-dataset-returns-Conflict-response.yml' not found: create one setting \`RECORD=true\` or ignore it using \`RECORD=none\`

Create a Data Access Control dataset returns "OK" response from Data Access Controls at features/v2/datasets.feature     (Fix with Cursor)

Cassette '/home/runner/work/datadog-api-client-ruby/datadog-api-client-ruby/cassettes/features/v2/datasets/Create-a-Data-Access-Control-dataset-returns-OK-response.yml' not found: create one setting \`RECORD=true\` or ignore it using \`RECORD=none\`

Delete a Data Access Control dataset returns "Bad Request" response from Data Access Controls at features/v2/datasets.feature     (Fix with Cursor)

Cassette '/home/runner/work/datadog-api-client-ruby/datadog-api-client-ruby/cassettes/features/v2/datasets/Delete-a-Data-Access-Control-dataset-returns-Bad-Request-response.yml' not found: create one setting \`RECORD=true\` or ignore it using \`RECORD=none\`

View all

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 25ecf46 | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback!}