Intermitent test failures in "should register all java commands"

On the build job, this only fails on Mac but I have been able to reproduce the failures locally as well on Linux.

1) Java Language Extension - Standard
       should register all java commands:
      AssertionError [ERR_ASSERTION]: Some Java commands are not registered properly or a new command is not added to the test.

...
...

      + expected - actual

         "java.action.showSupertypeHierarchy"
         "java.action.showTypeHierarchy"
         "java.apply.workspaceEdit"
         "java.clean.workspace"
      -  "java.edit.organizeImports"
         "java.execute.workspaceCommand"
         "java.ignoreIncompleteClasspath"
         "java.ignoreIncompleteClasspath.help"
         "java.open.clientLog"
--
         "java.open.serverLog"
         "java.project.addToSourcePath"
         "java.project.import"
         "java.project.listSourcePaths"
      -  "java.project.refreshDiagnostics"
         "java.project.removeFromSourcePath"
         "java.project.updateSourceAttachment"
         "java.projectConfiguration.status"
         "java.projectConfiguration.update"

  	at /Users/travis/build/redhat-developer/vscode-java/out/test/standard-mode-suite/extension.test.js:74:20

  	at processTicksAndRejections (internal/process/task_queues.js:97:5)

Start with out/test/standard-mode-suite/extension.test.js at the failing assertion and run the "should register all java commands" test on Mac and Linux. Compare the registered command list across runs to identify the intermittent difference; done means the test passes reliably on the affected platforms.