Suppressing GOMAXPROCS in info log

Is there any way to suppress the Leaving GOMAXPROCS=16: CPU quota undefined from info logs. Even if you define a value for GOMAXPROCS it gets logged with an indication that is inheriting/respecting the set value. Large logs are a pain to look at.

20:49:06 [Info] [Thread 0] Indexing file: packages/microsoft.win32.systemevents/6.0.0/microsoft.win32.systemevents.6.0.0.nupkg
20:49:07 [Info] Waiting for scan to complete on JFrog Xray...
20:49:07 [Info] Waiting for scan to complete on JFrog Xray...
20:49:10 [Info] 2024/06/06 20:49:04 maxprocs: Leaving GOMAXPROCS=16: CPU quota undefined

20:49:10 [Info] [Thread 2] Indexing file: packages/mono.texttemplating/2.2.1/mono.texttemplating.2.2.1.nupkg
20:49:11 [Info] Waiting for scan to complete on JFrog Xray...
20:49:12 [Info] 2024/06/06 20:49:06 maxprocs: Leaving GOMAXPROCS=16: CPU quota undefined

20:49:12 [Info] [Thread 1] Indexing file: packages/mstest.testadapter/3.1.1/mstest.testadapter.3.1.1.nupkg
20:49:13 [Info] Waiting for scan to complete on JFrog Xray...
20:49:16 [Info] 2024/06/06 20:49:10 maxprocs: Leaving GOMAXPROCS=16: CPU quota undefined

20:49:16 [Info] [Thread 2] Indexing file: packages/mstest.testframework/3.1.1/mstest.testframework.3.1.1.nupkg
20:49:17 [Info] Waiting for scan to complete on JFrog Xray...
20:49:17 [Info] 2024/06/06 20:49:06 maxprocs: Leaving GOMAXPROCS=16: CPU quota undefined

Search the Go repository for the Leaving GOMAXPROCS=16: CPU quota undefined message and trace how it reaches the CLI's info logger. Determine the intended suppression behavior and verify that the repeated maxprocs messages no longer appear without hiding the other informational log entries.