Expose CorrectHomographNumbers publicly on ILexEntry

[myieye]

Adds ILexEntry.CorrectHomographNumbers() which wraps the existing LexDb.CorrectHomographNumbers algorithm.
FieldWorks Lite writes HomographNumber directly and needs a way to trigger a "cleanup" of a potentially broken homograph sequence.

---

This change is 

[github-actions]

LCM Tests

    16 files  ±0      16 suites  ±0   3m 13s ⏱️ +16s
 2 860 tests +2   2 840 ✅ +2   20 💤 ±0  0 ❌ ±0 
11 388 runs  +8  11 220 ✅ +8  168 💤 ±0  0 ❌ ±0 

Results for commit b46e645. ± Comparison against base commit 66da667.

♻️ This comment has been updated with latest results.

[jasonleenaylor]

From an API standpoint I don't like adding a method on LexEntry which modifies data in other LexEntries. This should be exposed, but I don't think it belongs here.

@jasonleenaylor reviewed all commit messages and made 1 comment.
Reviewable status: 0 of 3 files reviewed, all discussions resolved.

[myieye]

@jasonleenaylor You're right. I moved it.

API-wise it would be arguably better to make the signature of my new method more similar to CollectHomographs in that it just takes a string form and morph-type. But it would be a bit awkward if it couldn't be used to correct blank-form entries. To do that it obviously needs the entry itself. If you're unhappy with it taking an entry and then also editing other entries. Then I can change it and make FW Lite handle the blank-form case. The current code would just be a bit more handy for us.

[jasonleenaylor]

@jasonleenaylor reviewed 4 files and all commit messages, and made 1 comment.
Reviewable status: 4 of 5 files reviewed, all discussions resolved.