[Global] Setting the activationEvents package.json parameter value to onStartupFinished

[FALLAI-Denis]

Description of the enhancement requested

Our VS Code Development Workshop, essentially based on IBM Z Open Editor, is becoming richer and richer by adding extensions from the marketplace or that we develop ourselves.

We are seeing increasingly long startup times and delays before being able to work with our Development Workshop...
We have analyzed the activation events associated with each VS Code extension.
The IBM Z Open Editor extension uses the * event (just like Zowe Explorer which is a prerequisite), so it is activated as soon as VS Code starts:

• is this a requirement?
• could the onStartupFinished event be sufficient?
• or onLanguage events for the different supported languages?

2025-01-10 21:30:41.147 [info] ExtensionService#_doActivateExtension Zowe.vscode-extension-for-zowe, startup: true, activationEvent: '*', root cause: IBM.zopeneditor
2025-01-10 21:30:45.226 [info] ExtensionService#_doActivateExtension IBM.zopeneditor, startup: true, activationEvent: '*'

Thanks.

[phaumer]

Zowe Explorer now activates with these settings:

  "activationEvents": [
    "onStartupFinished",
    "onFileSystem:zowe-ds",
    "onFileSystem:zowe-uss",
    "onFileSystem:zowe-jobs"
  ],

We can also add onStartupFinished, but it might even be that Z Open Editor is only activated once these have fired as we have a dependency, but I am not sure. I might be that our * activation triggers an early activation of Zowe Explorer. We will investigate.