Bump Metabase Version to v0.48.3

[SorenSpicknall]

Description

Resolves #3247

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?

On the test Metabase instance, I substituted the new version number for the existing one by hand. We currently don't deploy PR changes to the test instance because doing so on every commit to a PR would be costly and potentially harmful. After making the version change by hand, I monitored for application errors and confirmed that the postgres backup job is still functioning correctly for metabase-test. Everything seems to be in order.

Post-merge follow-ups

• No action required
• Actions required (specified below)

Monitor prod deployment for errors, including application errors and postgres backup issues.

[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.46.6.1
+           image: metabase/metabase:v0.48.3
            envFrom:
              - configMapRef:
                  name: metabase-config
            ports:
            - containerPort: 3000
...

[charlie-costanzo]

LGTM! Thank you for taking care of this!