Model Homograph number

Describe the feature
Entries disambiguate when they have the same headword by homograph number. In LCM that's in the ILexEntry.HomographNumber property. We should support this field in MiniLcm. It's not clear how to support this in harmony, but for now we can let there be duplicates, but when creating an entry the API should try to determine the next homograph number. This is done by checking to see if the headword is exactly the same as another one which exists in the db. A simple query like select max(homographNumber) from entries where headword = :newHeadword should give us the homograph number. We should only try to find it when the number from the API is 0 (or default if we let it be null)

Start in the MiniLcm entry-creation API and inspect how Entries are created and how HomographNumber is represented. Check the existing entry lookup or database query path for matching headwords, then verify that an explicit nonzero number is preserved while a zero or default value is derived from existing entries. Done means duplicate headwords receive the next homograph number without resolving Harmony support.