(Optional) limit on sampleRate for statsd input plugin

### Use Case

Currently when providing a high sample rate to `statsd` input plugin (e.g. `valid:0|ms|@0.000000001` ) it causes
https://github.com/influxdata/telegraf/blob/ee8dd87dd3f2683099de6ce33640d1b3cc7c3898/plugins/inputs/statsd/statsd.go#L870-L872

to "hang" quite a bit. Would it be "sensible" to enforce a reasonable limit on this number with the option to modify it?

### Expected behavior

Currently the main issue that this operation can take quite a bit of time. It is more of "preference" thing to fix/implement this.

### Actual behavior

It runs for quite some time

### Additional info

-

Start by reading plugins/inputs/statsd/statsd.go around lines 870-872, where the high sample rate causes the long-running operation. Determine a reasonable configurable limit for sampleRate and define completion as preventing excessive processing while preserving valid statsd input behavior.

Written by the indexing model from the issue text.