[Bug]: Collection v9.0 issues for backporting

[marianne013]

Search before creating an issue

• I have searched existing issues and confirmed this is not a duplicate

Bug Description

I would like to use this issue to track the bug fixes that need to be back ported to v9.0 to make it an "upgrade" release.
This is roughly what we found at Imperial, other admins might want to add their own issues.
These are the ones I remember as blockers:

• proxies accumulating in /tmp (Too many proxy files in /tmp --what is meant to provide clean up ? #8415)
  Also: 130bd6b
  Pull request: https://github.com/DIRACGrid/DIRAC/pull/8481/commits
• rogue opensearch indices (fix: isolate MonitoringReporter #8490) -- I think ?
• StorageManagementDB (Fix: do not need storage management db #8515)

Small, but annoying:

• MySQL.py: conn.ping(True) 07b3221

While we are at it:

• Unhelpful error message prolongs debugging: 55656bb

• ad07384 (We think this fixes the very occasional corruption we see in our FileCatalog.)

• This has been backported to v8, so also need v9.0 (RequestDB): 8ec1107

Steps to Reproduce

No response

Expected Behavior

No response

Actual Behavior

No response

Environment

No response

Relevant Log Output

Additional Context

First pull request:
#8550
addresses item "StorageManagementDB" and "MySql True" from above.

[fstagni]

#8550 merged, and v9.0.21 created (mostly to test the workflow). I let you handle the rest.
For cherry-picking PRs, please add the label "pr-sweep:ignore"

[marianne013]

I don't think I am allowed to label ?

[sfayer]

I don't think I am allowed to label ?

Hmm, I didn't think I could label, but it does seem like I can now.