fix concurrent writes to a framework in the custom framework tests

[api-clients-generation-pipeline[bot]]

See DataDog/datadog-api-spec#3829 Test branch datadog-api-spec/test/vbarth/fix-concurrent-writes

[datadog-datadog-prod-us1[bot]]

Datadog Report

All test runs 9c37fe1 :link:

:x: 5 Total Test Services: 4 Failed, 0 Passed

Test Services

Service Name	Failed	Known Flaky	New Flaky	Passed	Skipped	Total Time	Test Service View
surefirebooter11002032046684693339	6	0	0	1261	36	0s	Link
surefirebooter14859442464755784567	6	0	0	1261	36	0s	Link
surefirebooter2753362129899422604	6	0	0	1261	36	0s	Link
surefirebooter4864816336951742407	6	0	0	1261	36	0s	Link
org.codehaus.plexus.classworlds.launcher.launcher	0	0	0	0	0	4m 19.88s	Link

:x: Failed Tests (24)

This report shows up to 5 failed tests.

• Create a custom framework returns "Conflict" response - classpath:com/datadog/api/client/v2/api/security_monitoring.feature:Security Monitoring #2

• Create a custom framework returns "OK" response - classpath:com/datadog/api/client/v2/api/security_monitoring.feature:Security Monitoring #2

• Delete a custom framework returns "OK" response - classpath:com/datadog/api/client/v2/api/security_monitoring.feature:Security Monitoring #2

• Get a custom framework returns "OK" response - classpath:com/datadog/api/client/v2/api/security_monitoring.feature:Security Monitoring #2

• Update a custom framework returns "Bad Request" response - classpath:com/datadog/api/client/v2/api/security_monitoring.feature:Security Monitoring #2 - Details