dogwrap with StatsD instead of API

[2rs2ts]

Is your feature request related to a problem? Please describe.
I would like for application developers on my platform to be able to reuse old NRPE scripts to send check results to Datadog, but don't want to hand them API credentials; I want them to send to a DogStatsD endpoint we're running instead.

Describe the solution you'd like
I would like dogwrap to be able to send results to a given StatsD endpoint instead of having to use the API. If there are limitations that StatsD imposes–such an inability to send certain kinds of data–that is okay, they can just be documented. The core functionality seems like it can work with StatsD, and anything that wouldn't would probably be some edge case as far as my use case is concerned.

Describe alternatives you've considered
The alternative, and what I'll have to go with due to time constraints on my end, is a custom wrapper script that handles converting exit codes and such into StatsD events, service checks, etc.

Additional context
Due to my own time constraints, even though I could really benefit from dogwrap having this functionality, I almost certainly won't be able to create a PR for the change myself, so I'm only filing this feature request so that future users don't end up in a situation like mine.

I am aware that #298 exists, but the person who opened that issue obviously did not have the constraint of not wanting to give out API credentials to users, since they accepted the answer which would have required them to provide an API key.

Per the note in the issue template, I submitted a help ticket to let them know of this Github issue. I decided to make an issue, rather than just going through support, so that the general community could possibly benefit from the user story being written up.

[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.