update golang.org/x/{crypto,net,sys} and github.com/prometheus/client_golang

[cce]

Steps to reproduce:

go mod edit -go=1.23
go get golang.org/x/sys
go get golang.org/x/crypto
go get golang.org/x/net
go get github.com/prometheus/[email protected]
go mod tidy

also changed calls to renamed functions in updated github.com/prometheus/procfs package and related dependencies.

[algorandskiy]

I guess ubuntu 20.04 build image also needs to be upgraded

[gmalouf]

@onetechnical I think we should run this locally or in one of our build environments before updating packages in algod.

[jannotti]

What the heck is this doing?

[cce]

This was copied from prometheus#1364 which updated the upstream dependency, while fixing a rollover bug in the handling of some values collected. The function .Seconds() was removed from the upstream library, I think to force downstream consumers to do their own unit conversions (?). Because counters in Prometheus are meant to "roll over" to 0, usually when they hit some kind of max like MaxInt64, or otherwise, he is manually implementing a custom max here (Grafana and other systems handle metrics rollovers pretty well when deriving values like rates, etc). Since this is a float64 counter (I think for legacy reasons, this was a float before, so he is preserving its type?), I believe he wanted to pick a max value that would safely roll over. On his commit he left the comment Rollover counter automatically to avoid float64 accuracy issues. so I think he is trying to avoid some precision cliff?

[jannotti]

I think I get it. That value is probably the largest that can be represented precisely in a float64.