fix: require a strict majority to pass a gitvote vote

.gitvote.yml

@@ -15,6 +15,11 @@
 # plus, where this repo belongs to a subproject, the same two scoped to
 # that subproject's maintainer committee, for the case where this repo has
 # too few named owners to decide for itself.
+#
+# The thresholds are 50.01 and 66.66, not 50 and 66, because gitvote
+# passes a vote on >= rather than >: a flat 50 would let an even-sized
+# electorate tie and still pass. See cnpg-infra's
+# scripts/render-gitvote-config.sh for the full reasoning.
 automation:
   enabled: false
   rules:
@@ -24,7 +29,7 @@ automation:
 profiles:
   default:
     duration: 1w
-    pass_threshold: 50
+    pass_threshold: 50.01
     allowed_voters:
       teams:
         - cloudnative-pg-github-io-owners
@@ -34,7 +39,7 @@ profiles:
 
   component-owner:
     duration: 1w
-    pass_threshold: 66
+    pass_threshold: 66.66
     allowed_voters:
       teams:
         - cloudnative-pg-github-io-owners
@@ -44,7 +49,7 @@ profiles:
 
   committee:
     duration: 1w
-    pass_threshold: 50
+    pass_threshold: 50.01
     allowed_voters:
       teams:
         - community-ecosystem-maintainers
@@ -54,7 +59,7 @@ profiles:
 
   committee-component-owner:
     duration: 1w
-    pass_threshold: 66
+    pass_threshold: 66.66
     allowed_voters:
       teams:
         - community-ecosystem-maintainers