Reland Split mac clang-format sha1 per architecture

In preparation for using clang-format binaries built in clang rolls
which will result in per-arch clang-format executables, use different
sha1 files per architecture.

This updates the main chromium DEPS to use these, but many other
subprojects' DEPS also need to be updated, which will happen in separate
changes.

https://crrev.com/c/3529420 set the wrong output file name, it should
include the full path not just the base name.

Bug: 1286289
Change-Id: I32bd786948ea8f953a5d430e642dda0538dec7dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3533408
Reviewed-by: Hans Wennborg <hans@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Arthur Eubanks <aeubanks@google.com>
Cr-Commit-Position: refs/heads/main@{#982469}
NOKEYCHECK=True
GitOrigin-RevId: 6dbfc55643b3ffb84b2dab3b9e0d526bbb64cdee
diff --git a/mac/clang-format.arm64.sha1 b/mac/clang-format.arm64.sha1
new file mode 100644
index 0000000..6b3f7a9
--- /dev/null
+++ b/mac/clang-format.arm64.sha1
@@ -0,0 +1 @@
+5ba974b3b37f9f4e3b44fdde11d7ef2ab71619ab
diff --git a/mac/clang-format.x64.sha1 b/mac/clang-format.x64.sha1
new file mode 100644
index 0000000..6b3f7a9
--- /dev/null
+++ b/mac/clang-format.x64.sha1
@@ -0,0 +1 @@
+5ba974b3b37f9f4e3b44fdde11d7ef2ab71619ab