[🧹 CHORE]: Remove automaxprocs (uber) on Go 1.25 release

[rustatian]

No duplicates 🥲.

• I have searched for a similar issue.

What should be improved or cleaned up?

Go 1.25 introduces a cgroup-bound GOMAXPROCS, so no need to use automaxprocs from uber anymore:

On Linux, the runtime considers the CPU bandwidth limit of the cgroup containing the process, if any. If the CPU bandwidth limit is lower than the number of logical CPUs available, GOMAXPROCS will default to the lower limit. In container runtime systems like Kubernetes, cgroup CPU bandwidth limits generally correspond to the “CPU limit” option. The Go runtime does not consider the “CPU requests” option.