Remove webhook triggering run, redirect to trigger (#5084)

## What are you changing in this pull request and why?
Now that we natively support job chaining, we don't need the sample code
showing how to do it with a webhook.

## Checklist

Adding or removing pages (delete if not applicable):
- [x] Add/remove page in `website/sidebars.js`
- [x] Add an entry for deleted pages in `website/vercel.json`
- [x] Run link testing locally with `npm run build` to update the links
that point to deleted pages

website/docs/docs/deploy/deploy-jobs.md

@@ -105,7 +105,7 @@ Here are examples of cron job schedules. The dbt Cloud job scheduler supports us
 - `0 7 L * 5`: At 07:00 AM, on the last day of the month, and on Friday.
 - `30 14 L * *`: At 02:30 PM, on the last day of the month.
 
-### Trigger on job completion  <Lifecycle status="team,enterprise" /> 
+### Trigger on job completion  <Lifecycle status="team,enterprise" />
 
 To _chain_ deploy jobs together, enable the **Run when another job finishes** option and specify the upstream (parent) job that, when it completes, will trigger your job. You can also use the [Create Job API](/dbt-cloud/api-v2#/operations/Create%20Job) to do this.
 

website/vercel.json

@@ -574,7 +574,12 @@
     },
     {
         "source": "/guides/orchestration/webhooks/zapier-new-cloud-job",
-        "destination": "/guides/zapier-new-cloud-job",
+        "destination": "/docs/deploy/deploy-jobs#trigger-on-job-completion--",
+        "permanent": true
+    },
+    {
+        "source": "/guides/zapier-new-cloud-job",
+        "destination": "/docs/deploy/deploy-jobs#trigger-on-job-completion--",
         "permanent": true
     },
     {