Update NodeRevisionDelete:getCandidatesRevisionsByNids to only accept a single node ID

Problem/Motivation

To support query logic changes in ✨ Add support for "Maximum number allowed" revisions per content node translation Needs review and #3094354: Delete draft revisions safely → , I'm proposing to refactor NodeRevisionDelete:getCandidatesRevisionsByNids() as NodeRevisionDelete:getCandidatesRevisionsByNid() to only accept a single node id so that the query logic found within NodeRevisionDelete:getCandidatesRevisionsByNids() and use a subquery to only find translated revisions that are older than the current translation version.

Proposed resolution

This solution relies upon patch from #3127258-4: Replace CandidateNodesForm::submitForm usage of getCandidatesRevisionsByNids → to remove the only usage of NodeRevisionDelete:getCandidatesRevisionsByNids() with an array of node IDs. Once removed, we can refactor NodeRevisionDelete:getCandidatesRevisionsByNids() as NodeRevisionDelete:getCandidatesRevisionsByNid() to accept a single node id.

Remaining tasks

• Consensus
• Patch
• Feedback

User interface changes

None

API changes

Changes to NodeRevisionDelete interface and NodeRevisionDelete:getCandidatesRevisionsByNids().

Data model changes

None

Release notes snippet

TBD