Upgrade Metabase to v0.50.26.1

[ohrite]

Description

Metabase is currently out of date (0.48 vs v0.50) and the Slack integration surfaces a warning.

Resolves #3451

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?

This PR was tested according to the steps documented in runbooks/workflow/upgrade-metabase.md

Post-merge follow-ups

The new version will need to be rolled out to the cluster.

• No action required
• Actions required

[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:
...
        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
...
metabase-test, metabase, Deployment (apps) has changed:
...
        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
...

[themightychris]

Suggested change

	1. Visit the test instance at https://metabase-test.k8s.calitp.jarv.us/ to see that login and reporting work as expected
	2. Connect to the database instance `kubectl -n metabase-test exec -it database-0 -- bash`
	3. Ensure that `psql` can connect: `psql -U admin postgres`
	4. Scale the `metabase` ReplicaSet to zero: `kubectl -n metabase-test scale deployment metabase --replicas=0`
	5. Restore the dump to the test database: `cat pg_dumpall.sql | kubectl -n metabase-test exec -it database-0 -- psql -U admin postgres`
	6. Scale the `metabase ReplicaSet` to 1: `kubectl -n metabase-test scale deployment metabase --replicas=1`
	7. Ensure that the test instance still works
	1. Visit the test instance at https://metabase-test.k8s.calitp.jarv.us/ to see that login and reporting work as expected
	2. Ensure that `psql` can connect to the database instance. Enter `\q` to quit when finished:
	```bash
	kubectl -n metabase-test exec -it statefulset/database -- psql -U admin postgres
	```
	3. Scale the `metabase` ReplicaSet to zero: `kubectl -n metabase-test scale deployment metabase --replicas=0`
	4. Restore the dump to the test database: `cat pg_dumpall.sql | kubectl -n metabase-test exec -it database-0 -- psql -U admin postgres`
	5. Scale the `metabase ReplicaSet` to 1: `kubectl -n metabase-test scale deployment metabase --replicas=1`
	6. Ensure that the test instance still works