README.md mention for Go 1.25 automaxprocs

[mrwormhole]

README.md should probably mention this package is no longer needed after Go 1.25 (Aug 2025) release.

[frankjkelly]

Agreed. Following . . . .

[rabbbit]

See #96 (comment) - we plan to continue using this.

This being said, we could update the readme to call this out explicitly.

[AlexanderGrom]

I disagree that this package is no longer needed. My tests showed that Go 1.25 in kubernetes sets GOMAXPROCS=2 in containers with a limit of one CPU or less. As a result, trolling appears and the application works worse than with GOMAXPROCS=1.

I have concluded for ourselves that:

• Go 1.25: tries to prevent you from accidentally working in 1 thread.
• automaxprocs: tries to keep you from exceeding the actual CPU limit.

And in containers, the second is almost always more important.