chore(common): trigger core ci checks on developer changes

[jahorton]

I hope this is the right way to do things; the goal is to trigger Core CI checks whenever Developer changes are detected in order to prevent the scenario fixed by #11749 from going undetected again.

@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 - 18.0.53 (0.11750.11250)
• Keyboards
  • Test Keyboards
• Linux
  • Keyman for Linux: focal
  • Keyman for Linux: jammy
  • Keyman for Linux: mantic
  • Keyman for Linux: noble
  • Keyman for Linux: oracular
• macOS
  • Keyman for macOS
• Web
  • KeymanWeb Test Home
• Windows
  • Keyman for Windows
  • FirstVoices Keyboards for Windows
  • Text Editor (32 bit)
  • Text Editor (64 bit)

[mcdurdin]

I mean, this works, but it reflects an internal tangle of dependencies which it would be better to resolve if possible. After all, we shouldn't need developer to build core.

But it seems like we currently need developer in order to run core tests (which feels awkward). Two potentially better solutions:

1. In theory, we could restructure the tests to be a separate build configuration that depends on both core+developer.
2. We could use npx @keymanapp/kmc[@tier] to build keyboards used for Core tests.

But, we could accept this for now, and do this as future work (as I am not about to do it right now).

[mcdurdin]

I will review this once I am back on deck. I don't think it is urgent.

[mcdurdin]

OK, I have a clearer idea now of why I was feeling uncomfortable with this: this is testing some of the Developer cross-platform component build as a side-effect of building Core.

Instead, I would like to test the build of the cross-platform components of Developer as separate build configurations, rather than as a side-effect of testing Core. This will become more important as we move forward.

So I suggest we turn this into an issue to add 2 build configurations : Keyman Developer Test - Linux, Keyman Developer Test - mac, rather than adding Core test builds to the Developer triggers. This will then correspond with additional Release build configurations in the future to allow us to build distributions of Developer for those two platforms.

[jahorton]

Closing this in favor of issue #11755 per @mcdurdin's input.