Update nasm in CI to 3.01

Matches where Chromium is now. Hopefully we can switch to MASM and then
it'll be one less chore to manage.

Bug: 40259441
Change-Id: I8d0afdb7a5474adbf68b49c8433a450d3ede0b97
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/100467
Reviewed-by: Lily Chen <chlily@google.com>
Presubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: Lily Chen <chlily@google.com>

util/bot/UPDATING

diff --git a/util/bot/UPDATING b/util/bot/UPDATING
index 6d37c72..2bb00d3 100644
--- a/util/bot/UPDATING
+++ b/util/bot/UPDATING
@@ -20,7 +20,7 @@
     https://chromium.googlesource.com/chromium/deps/nasm/+/refs/heads/main/README.chromium
     Extract nasm.exe from the download named nasm-VERSION-win64.zip.
 
-    The current revision is nasm-2.13.03-win64.zip.
+    The current revision is nasm-3.01-win64.zip.
 
 Finally, update sde-linux64.tar.xz and sde-win32.tar.xz by downloading the
 latest release from Intel at

util/bot/nasm-win32.exe.sha1

diff --git a/util/bot/nasm-win32.exe.sha1 b/util/bot/nasm-win32.exe.sha1
index 62afef4..9bab962 100644
--- a/util/bot/nasm-win32.exe.sha1
+++ b/util/bot/nasm-win32.exe.sha1
@@ -1 +1 @@
-fe003e1128188bba6f54307802051f2eddfdee85
\ No newline at end of file
+78208cadc0a1574842a42711f1a3ed6e5aa8cfa1
\ No newline at end of file