Update Alerts and Providers to v1beta3 API

Notification-controller is introducing v1beta3 APIs for Alerts and
Providers. Update all the references to those APIs to use the new
version.

Signed-off-by: Sunny <darkowlzz@protonmail.com>

content/en/flux/cheatsheets/oci-artifacts.md

@@ -479,7 +479,7 @@ please see the [HelmChart documentation](/flux/components/source/helmcharts/#ver
 Configure alerting for when new artifacts are pulled and reconciled:
 
 ```yaml
-apiVersion: notification.toolkit.fluxcd.io/v1beta2
+apiVersion: notification.toolkit.fluxcd.io/v1beta3
 kind: Alert
 metadata:
   name: podinfo

content/en/flux/gitops-toolkit/packages.md

@@ -101,7 +101,7 @@ go get github.com/fluxcd/notification-controller/api
 Import package
 
 ```go
-import notificationv1b2 "github.com/fluxcd/notification-controller/api/v1beta2"
+import notificationv1b3 "github.com/fluxcd/notification-controller/api/v1beta3"
 ```
 
 and for `Receiver` objects:
@@ -115,8 +115,8 @@ API Types
 | Name                                               | Version |
 |----------------------------------------------------|---------|
 | [Receiver](../components/notification/receiver.md) | v1      |
-| [Provider](../components/notification/provider.md) | v1beta2 |
-| [Alert](../components/notification/alert.md)       | v1beta2 |
+| [Provider](../components/notification/provider.md) | v1beta3 |
+| [Alert](../components/notification/alert.md)       | v1beta3 |
 
 ### image.toolkit.fluxcd.io
 

content/en/flux/guides/helmreleases.md

@@ -552,7 +552,7 @@ the `flux-system` to start receiving notifications about the Helm
 release:
 
 ```yaml
-apiVersion: notification.toolkit.fluxcd.io/v1beta2
+apiVersion: notification.toolkit.fluxcd.io/v1beta3
 kind: Alert
 metadata:
   name: helm-podinfo

content/en/flux/monitoring/alerts.md

@@ -34,7 +34,7 @@ kubectl -n flagger-system create secret generic slack-bot-token \
 Create a notification provider for Slack by referencing the above secret:
 
 ```yaml
-apiVersion: notification.toolkit.fluxcd.io/v1beta2
+apiVersion: notification.toolkit.fluxcd.io/v1beta3
 kind: Provider
 metadata:
   name: slack-bot
@@ -57,7 +57,7 @@ For a complete list please see the [Provider `.spec.type` documentation](/flux/c
 Create an alert definition for all repositories and kustomizations:
 
 ```yaml
-apiVersion: notification.toolkit.fluxcd.io/v1beta2
+apiVersion: notification.toolkit.fluxcd.io/v1beta3
 kind: Alert
 metadata:
   name: on-call-webapp
@@ -199,7 +199,7 @@ The only caveat being that the provider address needs to point to the same
 git repository as the event source originates from.
 
 ```yaml
-apiVersion: notification.toolkit.fluxcd.io/v1beta2
+apiVersion: notification.toolkit.fluxcd.io/v1beta3
 kind: Provider
 metadata:
   name: flux-system
@@ -210,7 +210,7 @@ spec:
   secretRef:
     name: github
 ---
-apiVersion: notification.toolkit.fluxcd.io/v1beta2
+apiVersion: notification.toolkit.fluxcd.io/v1beta3
 kind: Alert
 metadata:
   name: podinfo
@@ -306,7 +306,7 @@ To display the Flux notifications on Grafana dashboards
 you can configure Flux to push events to Grafana annotations API:
 
 ```yaml
-apiVersion: notification.toolkit.fluxcd.io/v1beta2
+apiVersion: notification.toolkit.fluxcd.io/v1beta3
 kind: Alert
 metadata:
   name: grafana
@@ -320,7 +320,7 @@ spec:
       name: '*'
       namespace: flux-system
 ---
-apiVersion: notification.toolkit.fluxcd.io/v1beta2
+apiVersion: notification.toolkit.fluxcd.io/v1beta3
 kind: Provider
 metadata:
   name: grafana

content/en/flux/use-cases/gh-actions-helm-promotion.md

@@ -163,7 +163,7 @@ it performs a Helm release upgrade.
 Example of `clusters/staging/apps/demo-github.yaml`:
 
 ```yaml
-apiVersion: notification.toolkit.fluxcd.io/v1beta2
+apiVersion: notification.toolkit.fluxcd.io/v1beta3
 kind: Provider
 metadata:
   name: github
@@ -174,7 +174,7 @@ spec:
   secretRef:
     name: github-token
 ---
-apiVersion: notification.toolkit.fluxcd.io/v1beta2
+apiVersion: notification.toolkit.fluxcd.io/v1beta3
 kind: Alert
 metadata:
   name: demo-dispatch