Fix "command installer" specs

[mauricioszabo]

Thanks in advance for your bug report!

• Have you reproduced issue in safe mode?
• Have you used the debugging guide to try to resolve the issue?
• Have you checked our FAQs to make sure your question isn't answered there?
• Does your issue already exist?
• Have you checked you are on the latest release of Pulsar?

What happened?

Pulsar have a "command installer" that installs both ppm and pulsar in the PATH.

The problem is that the test (that resides here: https://github.com/pulsar-edit/pulsar/blob/master/spec/command-installer-spec.js) is insanely flaky. For example, it starts with:

     apmBinPath = path.join(
       resourcesPath,
       'app',
       'apm',
       'node_modules',
       '.bin',
       'apm'
     );

This is not the path anymore that we use. So I commented them for now, and we need a way to actually test the real command instead

Which OS does this happen on?

🍎 macOS

OS details

Any

Which CPU architecture are you running this on?

None

What steps are needed to reproduce this?

Run tests on CI

Additional Information:

No response

[confused-Techie]

This report is now bundled into a single issue #511