fix(cleanup): cleanup par + max batch size

[gurinderu]

Description

In this PR we fix the count of cleanup batch and parallelize deletion.

Motivation

If cleanup is slow it dramatically decreases the whole system performance.

Proposed Changes

• Make a cleanup batch smaller
• Parallelize deletion

Additional Notes

• Now par delete isn't limited by parallel factor, it means if the batch size is 1024 it will produce 1024 tasks and try to run them in parallel. As a result, it will spawn a lot of tasks on the blocking poll which utilize them fully, but it is ok.
• Also introduced an ActorKey which should be used as a datastore key in NET-632

Checklist

• The code follows the project's coding conventions and style guidelines.
• All tests related to the changes have passed successfully.
• Documentation has been updated to reflect the changes (if applicable).
• All new and existing unit tests have passed.
• I have self-reviewed my code and ensured its quality.
• I have added/updated necessary comments to aid understanding.

Reviewer Checklist

• Code has been reviewed for quality and adherence to guidelines.
• Tests have been reviewed and are sufficient to validate the changes.
• Documentation has been reviewed and is up to date.
• Any questions or concerns have been addressed.

[folex]

what is data: Vec<(String, PeerId)>?

[gurinderu]

Pairs of the particle id and worker id

[folex]

let's rename data argument to something sensible, otherwise it doesn't make any sense. Reads like you're going to clean up Vec<(String, PeerId)>

[gurinderu]

done