Central CouchDB migration to Alma 9

[amaltaro]

Impact of the new feature
CMSWEB CouchDB

Is your feature request related to a problem? Please describe.
Thanks to Aroosha for bringing this up to my attention last week.

Our current setup for CouchDB in testbed and production still relies on the RPM model, where the service is deployed directly in the host that runs SLC7. Given the EOL of SLC7 planned for end of June/2024, we need to find another solution for central CouchDB deployment.

Describe the solution you'd like
We have a few potential solutions for this:

1. start running CouchDB with Docker containers (as we already do for the cmsweb development clusters)
2. deploy CouchDB directly on top of the host OS
3. similar to 1, but instead use a dedicated kubernetes cluster for CouchDB

Given that the load of central CouchDB is much higher than any single agent, we will have to repeat the same performance evaluation considered in this ticket: #11567

PS.: Note that this ticket might become a meta issue.

Describe alternatives you've considered
See alternatives above.

Additional context
See list of dependencies in this link: https://docs.couchdb.org/en/stable/install/unix.html#dependencies