fix(web): use actual legacy model for legacy-model support unit tests

[jahorton]

Noticed this during work on epic-autocorrect when the "legacy model" tests failed from intermediate changes that shouldn't - and, in fact, didn't - apply to legacy models.

The TrieModel is non-legacy - it's very much updated for 14.0+ features. The old DummyModel, though... that one does not leverage 14.0+ features, thus can test those pathways. Sadly, it doesn't use keying - it just "dummies in" specific suggestions, so the corresponding legacy test (for use of keying) is now skipped.

@keymanapp-test-bot skip

[keymanapp-test-bot]

User Test Results

Test specification and instructions

User tests are not required

Test Artifacts

• Android
  • Keyman for Android apk
  • FirstVoices for Android 16.0 apk
  • FirstVoices Keyboards for Android apk
  • KeyboardHarness apk
  • Keyman for Android 16.0 apk
  • KMSample1 apk
  • KMSample2 apk
• Developer
  • Keyman Developer
  • Compiler Regression Tests
  • kmcomp.zip
• iOS
  • Keyman for iOS (simulator image)
  • FirstVoices Keyboards for iOS (simulator image)
  • TestFlight internal PR build version - 19.0.95 (0.14460.14109)
• Keyboards
  • Test Keyboards
• Web
  • KeymanWeb Test Home
• Windows
  • Keyman for Windows
  • FirstVoices Keyboards for Windows
  • Text Editor (32 bit)
  • Text Editor (64 bit)

[darcywong00]

Some nits about the PR title/body 😄

1. The title should start with an action word (instead of legacy model)
2. I see this ends up disabling the should compose suggestions from a fat-fingered keypress (keying needed) test because there's no suitable model for the test. Maybe we note this in the PR body.

[darcywong00]

lgtm

[jahorton]

2. I see this ends up disabling the should compose suggestions from a fat-fingered keypress (keying needed) test because there's no suitable model for the test. Maybe we note this in the PR body.

Will there ever be a suitable model? If not, shouldn't we just delete the test?

Thought about deleting, but it is a possible case. Not one we've been made aware of, of course - at this point, it'd only matter if someone out there actually did write and distribute their own custom model.

[mcdurdin]

Thought about deleting, but it is a possible case. Not one we've been made aware of, of course - at this point, it'd only matter if someone out there actually did write and distribute their own custom model.

I think then that we should delete it. We can always put it back if the need arises. Having skipped tests is just an unnecessary flag in test results otherwise.

[keyman-server]

Changes in this pull request will be available for download in Keyman version 19.0.95-alpha

[keyman-server]

Changes in this pull request will be available for download in Keyman version 19.0.95-alpha