Convention not followed about datadog-api-client-go

[tonglil]

Related to #1012, I don't understand how there are so many discrepancies when this library is autogenerated.

For example, this delete call doesn't accept an ID and require some kind of "body":
https://github.com/DataDog/datadog-api-client-go/blob/v1.1.0/api/v1/datadog/docs/SyntheticsApi.md#DeleteTests

But others act more like typical APIs:
https://github.com/DataDog/datadog-api-client-go/blob/v1.1.0/api/v1/datadog/docs/PagerDutyIntegrationApi.md#DeletePagerDutyIntegrationService
https://github.com/DataDog/datadog-api-client-go/blob/v1.1.0/api/v1/datadog/docs/MonitorsApi.md#DeleteMonitor

It's just so inconsistent which makes working with this library extremely difficult, especially given the fact that the docs and godocs for it are completely unnavigateable..

[github-actions]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[therve]

We evaluated this issue, and it comes down to compatibility now, so the trade off seems a bit too unbalanced. We'll keep this in mind when designing synthetics v2. Thanks.