chore: Switch to Lighthouse as default webhook provider

Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>

README.md

@@ -123,7 +123,7 @@ The following two paragraphs provide the full list of configuration and output v
 | velero\_ttl | The the lifetime of a velero backup to be set in the Velero Schedule CRD (see [default-backup.yaml](https://github.com/jenkins-x/jenkins-x-boot-config/blob/master/systems/velero-backups/templates/default-backup)) | `string` | `"720h0m0s"` | no |
 | version\_stream\_ref | The git ref for version stream to use when booting Jenkins X. See https://jenkins-x.io/docs/concepts/version-stream/ | `string` | `"master"` | no |
 | version\_stream\_url | The URL for the version stream to use when booting Jenkins X. See https://jenkins-x.io/docs/concepts/version-stream/ | `string` | `"https://github.com/jenkins-x/jenkins-x-versions.git"` | no |
-| webhook | Jenkins X webhook handler for git provider | `string` | `"prow"` | no |
+| webhook | Jenkins X webhook handler for git provider | `string` | `"lighthouse"` | no |
 | zone | Zone in which to create the cluster | `string` | `"us-central1-a"` | no |
 
 #### Outputs

variables.tf

@@ -120,7 +120,7 @@ variable "lets_encrypt_production" {
 variable "webhook" {
   description = "Jenkins X webhook handler for git provider"
   type        = string
-  default     = "prow"
+  default     = "lighthouse"
 }
 
 variable "version_stream_url" {