Bib 809 machine translation scoring

[kaseywright]

This PR addresses the need to evaluate the effectiveness of machine translations and human edits by determining the similarity between two versions of a resource. To achieve this, we will utilize the Levenshtein Distance algorithm, a measure of the minimum number of single-character edits (insertions, deletions, or substitutions) required to change one string into another.

The PR includes a Levenshtein Distance implementation and the necessary utility methods to effectively score long resources. A new queue, generate-resource-content-similarity-score, has been created, along with a corresponding message, publisher, and subscriber. The message will contain information about the resource content versions being compared, including the type of comparison being performed, as designated by one of the values in the ResourceContentVersionSimilarityComparisonTypes enum. This allows the subscriber to run the appropriate logic for the resource content types being compared.

[linear]

BIB-809 Machine Translation Scoring

[kaseywright]

Bump @jwinston-bn @NateMerritt

[jwinston-bn]

I generally would like to have the Async suffix on any async methods for consistency (like ProcessAsync above).

And personal preference, I wouldn't typically include types in method names where it can be implied by the return type. This is kind of like if the score were an int, and the method was GenerateSimilarityScoreInt. I would just call it GenerateSimilarityScoreAsync.

[jwinston-bn]

Would like to see if we can get this using the object references, rather than using this Join operator.

x => x.ResourceContentVersion.ResourceContentVersionSnapshots