Refactor mac signing scripts for development workflow

chrome/installer/mac/variables.sh

Index: chrome/installer/mac/variables.sh
diff --git a/chrome/installer/mac/variables.sh b/chrome/installer/mac/variables.sh
new file mode 100644
index 0000000000000000000000000000000000000000..c38d1dce209a6f7d58fae09a1cdba9fe766cc689
--- /dev/null
+++ b/chrome/installer/mac/variables.sh
@@ -0,0 +1,12 @@
+# Copyright 2017 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+enforcement_flags_app="restrict"
+enforcement_flags_helpers="${enforcement_flags_app},library"
+
+requirement_suffix="and certificate leaf=H\"605852E8A609E39F8CF795E396657D26B3A031BC\""

[Mark Mentovai, 2017/04/24 15:00:23]

What you upload and submit for review should only ever show what you want to
check in (unless you’ve clearly marked something “not for checkin”). This
certainly isn’t suitable for checkin.

Let’s say that I was a terrible reviewer who stamped this without scrutinizing
it, and you got excited so you ticked the commit checkbox, because it’s been a
long weekend and you forgot that you had left this development stuff behind. It
lands in the tree, and official signing starts failing. Oh no!

[Greg K, 2017/04/25 00:55:01]

Acknowledged.

+#requirement_suffix="\
+#and (certificate leaf = H\"85cee8254216185620ddc8851c7a9fc4dfe120ef\" or \
+#certificate leaf = H\"c9a99324ca3fcb23dbcc36bd5fd4f9753305130a\") \
+#"

[Mark Mentovai, 2017/04/24 15:00:23]

We also have sign_installer_tools.sh. Should it get in on the action?

[Greg K, 2017/04/25 00:55:01]

Done.