ops: cap deployment revision history to 5

What changed: set revisionHistoryLimit: 5 on all tracked Deployment manifests so old ReplicaSets do not accumulate beyond five revisions per workload.

How verified: confirmed every Deployment manifest in services/ and infrastructure/ now includes revisionHistoryLimit: 5 and reviewed the resulting diff.

Author: soohyunme

infrastructure/base/monitoring/gatus/base/deployment.yaml

@@ -4,6 +4,7 @@ metadata:
   name: gatus
   namespace: monitoring
 spec:
+  revisionHistoryLimit: 5
   replicas: 1
   selector:
     matchLabels:

services/event-bingo/base/backend-deployment.yaml

@@ -3,6 +3,7 @@ kind: Deployment
 metadata:
   name: event-bingo-backend
 spec:
+  revisionHistoryLimit: 5
   replicas: 1
   strategy:
     type: Recreate

services/event-bingo/base/frontend-deployment.yaml

@@ -3,6 +3,7 @@ kind: Deployment
 metadata:
   name: event-bingo-frontend
 spec:
+  revisionHistoryLimit: 5
   replicas: 1
   selector:
     matchLabels:

services/experiment-platform-pseudolab/base/backend-deployment.yaml

@@ -3,6 +3,7 @@ kind: Deployment
 metadata:
   name: experiment-platform-backend
 spec:
+  revisionHistoryLimit: 5
   replicas: 1
   selector:
     matchLabels:

services/experiment-platform-pseudolab/base/frontend-deployment.yaml

@@ -3,6 +3,7 @@ kind: Deployment
 metadata:
   name: experiment-platform-frontend
 spec:
+  revisionHistoryLimit: 5
   replicas: 1
   selector:
     matchLabels:

services/homepage/base/deployment.yaml

@@ -5,6 +5,7 @@ kind: Deployment
 metadata:
   name: homepage-api
 spec:
+  revisionHistoryLimit: 5
   replicas: 1
   selector:
     matchLabels:
@@ -42,6 +43,7 @@ kind: Deployment
 metadata:
   name: homepage-frontend
 spec:
+  revisionHistoryLimit: 5
   replicas: 1
   selector:
     matchLabels: