CouchDB no longer supports all_or_nothing option for bulk_docs API

[amaltaro]

Impact of the new feature
WMCore in general (likely used by local/global workqueue and wmstats)

Is your feature request related to a problem? Please describe.
This all_or_nothing bulk operation option has been removed in CouchDB 2.0, see:
https://docs.couchdb.org/en/latest/whatsnew/2.0.html#upgrade-notes

As we migrate to CouchDB 3.x, we need to update our code such that we can keep remain as close as possible to an atomic transaction, even when multiple documents are created or updated.

Describe the solution you'd like
According to this documentation: https://docs.couchdb.org/en/latest/api/database/bulk-api.html#db-bulk-docs
we can make a nested dictionary/json with all the documents that we want to create or update in CouchDB. This should bring us closer to the all_or_nothing deprecated functionality (if not the same behavior).

So, the expected changes with this ticket are:

• remove all the places defining this all_or_nothing flag
• and update our CMSCouch code performing bulk operations such that it provides the correct data format to the bulk_docs API, a list of documents to be created/updated.

Describe alternatives you've considered
Max provided an initial proposal for fixing this, in: #10780

Additional context
A sub-task of #8853

[amaltaro]

Moving it under the Waiting column because it can only go in once we migrate to CouchDB 3.x