refactor(developer): use npm or local source for server addons instead of github references

[mcdurdin]

Brings trayicon source into the repository, as the source repo appears to be dead. Updates console source to latest version on npm.

Opted not to bring the source into the repo rather than keep in a separate repo because npm doesn't behave well with git/https links, and we don't want to publish yet another package.

Fixes: #12077

User Testing

• TEST_SERVER: In Keyman Developer, verify that Keyman Developer Server is working correctly.
• TEST_SERVER_TRAY_ICON: In Keyman Developer, verify that the Server icon is accessible in the System Notification Area.
• TEST_SERVER_CONSOLE_WINDOW: In Keyman Developer, verify that Hide/Show Console window functions work in the Server icon menu.

[keymanapp-test-bot]

User Test Results

Test specification and instructions

• ✅ TEST_SERVER (PASSED) (notes)
• ✅ TEST_SERVER_TRAY_ICON (PASSED) (notes)
• 🟩 TEST_SERVER_CONSOLE_WINDOW (SKIPPED): )

Test Artifacts

• Developer
  • Keyman Developer
  • Compiler Regression Tests
  • kmcomp.zip
• Keyboards
  • Test Keyboards

[mcdurdin]

Server is failing to start on the build associated with 38d043c:

C:\Program Files (x86)\Keyman\Keyman Developer\Server>..\node.js\node.exe .
node:internal/errors:490
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@keymanapp/common-types' imported from C:\Program Files (x86)\Keyman\Keyman Developer\Server\node_modules\@keymanapp\developer-utils\build\src\types\kpj\kpj-file-reader.js
    at new NodeError (node:internal/errors:399:5)
    at packageResolve (node:internal/modules/esm/resolve:889:9)
    at moduleResolve (node:internal/modules/esm/resolve:938:20)
    at defaultResolve (node:internal/modules/esm/resolve:1153:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:838:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
    at link (node:internal/modules/esm/module_job:76:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v18.14.1

[dinakaranr]

Test Results

I tested the PR #12090 task today using the Keyman 18.0.81-alpha-test-12090 build. I repeatedly get the confirm dialog after clicking the "Test Keyboard on Web" button. Hence, I am unable to launch the keyboard on the browser (localhost:8008). I observed this behavior on Windows 10 and 11 OSs. So, I am unable to proceed with the testing. Hence, I failed this PR. Thank you.

• TEST_SERVER (Failed):
• TEST_SERVER_TRAY_ICON (Failed):
• TEST_SERVER_CONSOLE_WINDOW (Failed):

[mcdurdin]

Note: force push to cleanup commit history on developer/src/kmc/test/fixtures/get-last-git-commit-date/README.md, which was involved in a throwaway non-merge commit (d8986be), breaking the unit test. (Yeah, this test is a bit fragile, I guess we could mock the call to git -- which makes it a unit test rather than an integration type test -- but it seemed important to me to test that we were actually using git correctly too.)

[mcdurdin]

Latest build:

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'restructure' imported from C:\Program Files (x86)\Keyman\Keyman Developer\server\node_modules\@keymanapp\developer-utils\build\src\types\kmx\kmx-builder.js
←[90m    at new NodeError (node:internal/errors:399:5)←[39m
←[90m    at packageResolve (node:internal/modules/esm/resolve:889:9)←[39m
←[90m    at moduleResolve (node:internal/modules/esm/resolve:938:20)←[39m
←[90m    at defaultResolve (node:internal/modules/esm/resolve:1153:11)←[39m
←[90m    at nextResolve (node:internal/modules/esm/loader:163:28)←[39m
←[90m    at ESMLoader.resolve (node:internal/modules/esm/loader:838:30)←[39m
←[90m    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)←[39m
←[90m    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)←[39m
←[90m    at link (node:internal/modules/esm/module_job:76:36)←[39m {
  code: ←[32m'ERR_MODULE_NOT_FOUND'←[39m
}

[mcdurdin]

@dinakaranr I have resolved the issues that were blocking user test. Would you be able to re-test? Thanks!

@keymanapp-test-bot retest all

[dinakaranr]

Test Results

I tested this issue with the attached "Keymandeveloper-18.0.87-Alpha-test-12090" build on the Windows 10 and 11 OS environments: Here is my observation.

• TEST_SERVER (passed): 

1. I installed the "keymandeveloper-18.0.87.exe" file.
2. Double-click on the "Keyman Developer" icon.
3. The developer tool appeared correctly.
4. Open the Keyman keyboard project (*.kpj) file.
5. Open any keyman keyboard (*.kmn) file. (e.g., gff_amharic.kmn).
6. Navigate to the Debugger mode by pressing the F5 or (On build tab/Start debugging).
7. Navigate to the layout tab. The debugger works well.
8. Click on an empty text box. I can enter some text.
9. Click the "Test Keyboard on Web" button to start the web keyboard server.

• TEST_SERVER_TRAY_ICON (passed): 

1. The server icon appears in the tray. 
2. Click on the server icon. It shows the four options. 

• Open http://localhost:8008 in the "http://localhost:8008 in browser".
• Show Console.
• Hide Console.
• Exit Keyman Development Server.

• TEST_SERVER_CONSOLE_WINDOW (failed): 

1. Click the "http://localhost:8008 in browser" option.
2. Observe that the web keyboard opened on the browser.
3. Click the "Show Console" option. observed that the "Power Shell" window does not open for the first click. but it is opening for the second time.
4. Click the "Hide Console" option. I observed that the "Power Shell" window closed automatically.
5. Click "Exit Keyman Development Server" and observe that the icon disappeared from the tray.
6. I failed this scenario because the "Power Shell" window does not open for the first click.

[mcdurdin]

• TEST_SERVER_CONSOLE_WINDOW (failed):

1. Click the "http://localhost:8008 in browser" option.
2. Observe that the web keyboard opened on the browser.
3. Click the "Show Console" option. observed that the "Power Shell" window does not open for the first click. but it is opening for the second time.
4. Click the "Hide Console" option. I observed that the "Power Shell" window closed automatically.
5. Click "Exit Keyman Development Server" and observe that the icon disappeared from the tray.
6. I failed this scenario because the "Power Shell" window does not open for the first click.

Thank you for the test @dinakaranr and picking this up. It turns out that this issue is already being tracked:

• bug(developer): 'Show Console' menu for Server has to be selected twice for the console to show #9694

As the problem is not new to this PR, and is not major I will mark this as 'SKIPPED' and go ahead and merge:

TEST_SERVER_CONSOLE_WINDOW (skipped)

[keyman-server]

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