Configuration option to drop oldest or newest data in the buffer when buffer is full

[kj4tmp]

Use Case

Similar to #15208

(accommodating temporary high-write bursts to and influxdb instance)

Sometimes the newest data is more important to keep than the oldest data (if your computer failed, would you care more about what happened right before the failure or 5 minutes before the failure?)

Sometimes the oldest data is more important to keep than the newest data (ex: which events happened first in this very large burst of events?)

Expected behavior

I expected to see a configuration option like "buffer_drop_strategy" which would default to "drop_oldest".

Actual behavior

No configuration option to specify which metrics (newest or oldest) are dropped from the buffer.

Additional info

No response

[powersj]

Similar to #15208, not opposed to do this as well. We would want to add an option for this as a part of the buffer management re-write.