fix(k8s): use Recreate strategy to deploy updates

[themightychris]

Description

While watching the latest Metabase update deploy, I noticed that we don't have the Metabase deployment explicitly set to use the Recreate strategy, allowing replicas of different versions to run at the same time under the default rolling strategy

While deploying new versions, it is lower risk to shut down all the old version instances before spinning up the first new version instance and running migrations. This will result in a longer period of Metabase not being available (low minutes) but ensure no issues are created by Metabase's config database being simultaneously written to by different versions of Metabase.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

How has this been tested?

PR preview action will show applied change

Post-merge follow-ups

• Watch the post-merge deployment of this PR shut down all metabase pods before spinning up new ones

[github-actions]

The following changes will be applied to the production Kubernetes cluster upon merge.

BE AWARE this may not reveal changes that have been manually applied to the cluster getting undone—applying manual changes to the cluster should be avoided.

metabase, metabase, Deployment (apps) has changed:
...
    namespace: metabase
    labels:
      name: metabase
  spec:
    replicas: 3
+   strategy:
+     type: Recreate
    selector:
      matchLabels:
        name: metabase
    template:
      metadata:
...
metabase-test, metabase, Deployment (apps) has changed:
...
    namespace: metabase-test
    labels:
      name: metabase
  spec:
    replicas: 1
+   strategy:
+     type: Recreate
    selector:
      matchLabels:
        name: metabase
    template:
      metadata:
        labels:
          name: metabase
      spec:
        containers:
          - name: metabase
-           image: metabase/metabase:v0.48.3
+           image: metabase/metabase:v0.50.26.1
            envFrom:
              - configMapRef:
                  name: metabase-config
            ports:
            - containerPort: 3000
...