Set MaxOpsPerSec on bulk operation options for outbox cleanup

[ramonsmits]

It was advised by Grisha from RavenDB to add a MaxOpsPerSec value to the bulk operation options for outbox cleanup:

https://github.com/Particular/NServiceBus.RavenDB/blob/7ac3cd1b5c443bf836d91c211db248cbff2b8ec7/src/NServiceBus.RavenDB/Outbox/OutboxRecordsCleaner.cs#L38-L44

After requesting guidance on the value to use it is clear that:

• If the average message processing rate per second is higher that the configured value for MaxOpsPerSec that outbox document deletions will lag behind inserts.
• A global default cannot be configured for this argument
• Specifying a high value is considered better by RavenDB as that prevents the database from suffocating the system host of resources.

[danielmarbach]

Discussed this with Ramon. We switched away from DeleteByIndex to use DeleteByQueryOperation as the documentation states

Batching and Concurrency The deletion of documents matching a specified query is run in batches of size 1024. RavenDB doesn't do concurrency checks during the operation so it can happen than a document has been updated or deleted meanwhile.

https://ravendb.net/docs/article-page/4.2/Csharp/client-api/operations/delete-by-query

the batch size is already 1024 and handled efficiently by the server. Since we do not backport performance enhancements I'm going to close this one.