ci: don't use redict during Forgejo testing (#13116)

`registry.redict.io/redict:7.3.0-scratch` image is no longer available resulting in [build errors](https://codeberg.org/forgejo/forgejo/actions/runs/170823/jobs/7/attempt/1).  This PR removes redict from the testing matrix, and replaces it with redis for the coverage testing.

redict does not appear to be an active project, with no updates in 8 months: https://codeberg.org/redict/redict

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/13116
Reviewed-by: Andreas Ahlenstorf <aahlenst@noreply.codeberg.org>

.forgejo/workflows/coverage.yml

@@ -58,7 +58,7 @@ jobs:
           POSTGRESQL_EXTRA_FLAGS: -c full_page_writes=off
         options: --tmpfs /bitnami/postgresql
       cacher:
-        image: registry.redict.io/redict:7.3.6-scratch
+        image: data.forgejo.org/oci/bitnami/redis:7.2
         options: --tmpfs /data:noatime,uid=1000,gid=1000
     steps:
       - uses: https://data.forgejo.org/actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3

.forgejo/workflows/testing.yml

@@ -161,9 +161,6 @@ jobs:
           - name: redis
             image: data.forgejo.org/oci/bitnami/redis:7.2
             options: --tmpfs /bitnami/redis/data:noatime
-          - name: redict
-            image: registry.redict.io/redict:7.3.0-scratch
-            options: --tmpfs /data:noatime
           - name: valkey
             image: data.forgejo.org/oci/bitnami/valkey:7.2
             options: --tmpfs /bitnami/redis/data:noatime