Golang bytes: IndexByte can return -4294967295 when memory usage is above 2^31 on js/wasm [1.22 backport]

@randall77 requested issue #65571 to be considered for backport to the next 1.22 minor release.

@gopherbot please open backport issues.

This bug causes {bytes,string}.Index functions to return wrong results when used with very large arguments.

Comment From: gopherbot

Change https://go.dev/cl/598975 mentions this issue: [release-branch.go1.22] internal/bytealg: extend memchr result correctly on wasm

Comment From: gopherbot

Closed by merging CL 598975 (commit 9e148a4150ece0c24e60197893c8821b2c67e151) to release-branch.go1.22.