[QT-353] Use a different approach to branch restrictions (hashicorp#1…

…7998) (hashicorp#18059)

Create a new workflow job that is only triggered when all build and
integration workflows have completed. This will allow us to require
branch restrictions on a single workflow.

Of note, we tried to allow docs branches to bypass testing using the
method suggested by Github[0], however, the `branches-ignore`
functionality did not work for the `pull_request` event type. Therefore,
bypassing build and integration workflows for docs branches is no longer
supported.

[0] https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks

Signed-off-by: Ryan Cragun <[email protected]>

.github/workflows/build.yml

@@ -1,15 +1,9 @@
+---
 name: build
 
 on:
   workflow_dispatch:
   pull_request:
-    types:
-      - opened
-      - reopened
-      - synchronize
-    branches-ignore:
-      - docs/**
-      - backport/docs/**
   push:
     branches:
       - main
@@ -200,3 +194,16 @@ jobs:
       artifact-revision: ${{ needs.product-metadata.outputs.vault-revision }}
       artifact-version: ${{ needs.product-metadata.outputs.vault-version }}
     secrets: inherit
+
+  completed-successfully:
+    runs-on: ubuntu-latest
+    needs:
+      - build-other
+      - build-linux
+      - build-darwin
+      - build-docker
+      - build-ubi
+      - enos
+      - enos-docker-k8s
+    steps:
+      - run: echo "All build and integration workflows have succeeded!"