Add 3 pod redundancy to deployment

As per email:

> Running a single pod means your application has no redundancy and if that pod goes down, your application goes down with it. We recommend a [minimum of 3 pods](https://developer.gov.bc.ca/docs/default/component/platform-developer-docs/docs/automation-and-resiliency/app-resiliency-guidelines/#a-highly-available-application) for production deployments. It's also worth noting that due to regular OpenShift cluster maintenance, pods can be evicted or shut down at any time, so a single-pod deployment that has been stable so far may still experience an outage in the future. Single pod deployments may be down for as much as 10% of the time, whereas multi-node deployments benefit from 99.5% target uptime on Silver.

We need to change our deployment to meet this minimum.

Requirements before this change:
* Profile resource usage on a single pod;
* cpu usage idle/intersecting
* ram usage idle/intersecting
* storage usage
* forecast expected peak usage;
* Probably 2-4 simultaneous users

Start by locating the deployment configuration and profile the current single pod's CPU, RAM, and storage usage during idle and interacting workloads. Forecast peak demand for the expected 2–4 simultaneous users, then verify the deployment runs at least three pods while remaining within the measured resource limits.

Written by the indexing model from the issue text.