Hold memcached at jammy in noble-caracal bundles

The memcached machine used the noble default while memcached was focal, so deploy failed on a base mismatch. Hold memcached at jammy, matching the other charms.

Change-Id: I582c23d979f8664d74d505d95cdac3b7f9645664
Signed-off-by: Seyeong Kim <seyeong.kim@canonical.com>

src/tests/bundles/noble-caracal-s3.yaml

@@ -20,7 +20,7 @@ machines:
   8: {}
   9: {}
   10:
-    series: noble
+    series: jammy
 
 # We specify machine placements for these to improve iteration
 # time, given that machine "0" comes up way before machine "6"
@@ -78,8 +78,8 @@ applications:
   memcached:
     charm: ch:memcached
     num_units: 1
-    # Note that holding memcached at focal as it's not available at jammy yet.
-    series: focal
+    # Note that holding memcached at jammy as it's not available at noble yet.
+    series: jammy
     to:
       - '10'
   #swift-proxy is used to test gnocchi against an S3 storage backend

src/tests/bundles/noble-caracal.yaml

@@ -23,7 +23,7 @@ machines:
   '11':
   '12':
   '13':
-    series: noble
+    series: jammy
 
 # We specify machine placements for these to improve iteration
 # time, given that machine "0" comes up way before machine "6"
@@ -108,8 +108,8 @@ applications:
   memcached:
     charm: ch:memcached
     num_units: 1
-    # Note that holding memcached at focal as it's not available at jammy yet.
-    series: focal
+    # Note that holding memcached at jammy as it's not available at noble yet.
+    series: jammy
     to:
       - '13'