Add support for "Maximum number allowed" revisions per content node translation

The merge request diff applies against latest rc6 but there is a message in the merge request that it needs a rebase against the main branch.

We just added a 2.x version of the module. This is a complete rewrite based on plugins to determine which revisions can be deleted. It also uses a queue worker to actually delete revisions, and takes multiple translations of content into account. Could you please test if this solves the issues you currently experience?

For me, the new version 2.x does not work. Previously, too many revisions were deleted. But now too few revisions are deleted. At least that's how it looks.
In the sandbox, the module works great at first sight. But in our system with two languages and 40k revisions, it doesn't seem to work. Too bad!

I confirm what @vincent.hoehn say: the 2.x version does not work at all, if I specify to keep only 1 revision, nothing happens.

For example, I have a node with 2860 revisions, none is deleted.

For those whose need the patch for -rc6.

@vincent.hoehn @B-Prod could you maybe try and debug what is happening in the 2.x version to see why the revisions are not being deleted? Are you getting errors in the logs? Are items being added to the queue? Is the queue being processed? Is this process running out of memory? Any additional info to help resolve the issues would be appreciated!

#42 looks like working with 1.0 rc-7.

I have now check and calculate revisions count per node and node translations after clicking delete revisions on node.

#42 has one code change is missing from #37,
File CandidateNodesForm.php has below mentioned change inside the #37 patch, but which is missing inside the #42 patch i have added that change and created new patch and other changes are same as #42 and tested with latest version of module 8.x-1.-rc7.

Closing because the current development is being made in branch 2.x