Adjust the latency_fanout with some very unscientific values

[mattdurham]

PR Description

Which issue(s) this PR fixes

The default buckets ended at 10 seconds and the write path can take much longer than that. Chose 300s (5m) as the max since anything above that hits the staleness marker and would be a really bad indicator.

Notes to the Reviewer

PR Checklist

• CHANGELOG.md updatedad

[rfratto]

Haha I don't want to have to change this again after we find out we need more specific buckets. Can you ask around how we should distribute buckets for a histogram? It would be good knowledge for us to have in general going forward.

(Or is this an opportunity for us to use native histograms, even? 👀)

[github-actions]

This PR has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If you do not have enough time to follow up on this PR or you think it's no longer relevant, consider closing it.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your PR will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!

[github-actions]

This PR has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If you do not have enough time to follow up on this PR or you think it's no longer relevant, consider closing it.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your PR will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!

[rfratto]

I'm going to close this for now as stale. If we want to pick this back up, I think we should move the PR to the Alloy repo and then consider whether it should be backported here.