Test MiniLcm morph type APIs

[hahn-kev]

After #1846 is completed we should write MiniLcm base tests to ensure our APIs work. Note we may want to not test the create morph type API in the FW version.

[rmunn]

Note that we may need tests as mentioned in #1857 (comment)

[rmunn]

One thing we may not be handling yet, which we will definitely need a test for, is the changes to an entry that can happen when a morph type is changed. Some morph type modifications cause FieldWorks Classic to pop up a notification saying "Some grammatical information will be lost! Do you still want to continue?" For example, affix morph types can be set as being derivational affixes, meaning that they have "From" and "To" grammatical info. (Like the -ly suffix in English that changes an adjective to an adverb). If you change the morph type from an affix to a non-affix, then the "Some info will be lost" dialog pops up, and the grammatical info of the "To" is the only one kept (the "From" is discarded).

We'll need to write some tests dealing with derivational affixes, and make sure that our logic does the same thing that FieldWorks Classic does when a morph type is updated (for example, if we kept the "From" grammatical info then the test should fail).

[rmunn]

The place to look in the FieldWorks Classic source code is in the ChangeAffixToStem and ChangeStemToAffix methods of MorphTypeAtomicLauncher. It's found under Src/Common/Controls/DataControlsMorphTypeAtomicLauncher.cs.

In exploring, I also found out how the list of available morph types is populated in FLEx when you want to change the morph type of an entry. Simple version is, depends on whether it's an affix or not. The more complicated version involves looking for ReferenceTargetCandidates methods in the OverridesLing_MoClasses.cs file in liblcm. But for the sake of simplicity, I think FW Lite can settle for defaulting to "you can change an affix to another affix, or a non-affix to another non-affix", and then if you want to change a non-affix (say, a stem or root) to an affix, then it involves checking a box.