perf: Use distributed cache for no media paths

[juliusknorr]

Local cache is not ideal as it is in most cases with APCu limited in since and on systems with lots of users and with load balanced webserver nodes it is not likely that this cache is hit.

Moving to a distributed one should make sure this is more likely to have a cache hit on big instances and overhead to the distributed should be ok with a page load request doing one cache check

[juliusknorr]

/backport to stable32 please

[juliusknorr]

/backport to stable31 please

[backportbot]

The backport to stable31 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable31
git pull origin stable31

# Create the new backport branch
git checkout -b backport/3328/stable31

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 5c67c5a0

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/3328/stable31

Error: Failed to check for changes with origin/stable31: No changes found in backport branch

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[juliusknorr]

/backport to stable30 please

[backportbot]

The backport to stable30 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable30
git pull origin stable30

# Create the new backport branch
git checkout -b backport/3328/stable30

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 5c67c5a0

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/3328/stable30

Error: Failed to check for changes with origin/stable30: No changes found in backport branch

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.