Restore ability for packages to focus specs…

[savetheclocktower]

…on both Jasmine 1 and Jasmine 2 test runners.

Also restore behavior of failing immediately in CI if a test is accidentally left focused.

These were some loose ends left over from #990. Focusing specs (changing it to fit or describe to fdescribe) was already working within Pulsar's own test suite for Jasmine 2 tests, but not on package specs running Jasmine 2, nor on package specs running Jasmine 1.

I don't like it when my head hurts, so I've not delved too deeply into determining how the core suite was able to use fit (despite the fact that I couldn't figure out how or where it was defined) but not a package. I just know that the jasmine-focused and jasmine2-focused packages solve this for Jasmine 1 and 2, respectively.

The Jasmine 2 runner also needed a way to fail the tests in CI if any test was accidentally left focused. I found this out the hard way when that very thing happened to me in #1249.

[DeeDeeG]

Looks basically reasonable, I think? Large linter diff is kinda distracting on a PR like this, I am highly tempted to offer to split those off to a separate commit or yeet those parts of the diff if you don't mind. I could force push the branch even?

EDIT: If I am reading correctly, spec/runners/jasmine1-test-runner.js may be only whitespace changes, it should be fairly easy to exclude that file from the commit. I can easily offer to do that much at least.

EDIT 2: Of course, there's the require('jasmine-focused');. Anyhow, I can offer to split those changes to their own commit.

[savetheclocktower]

Looks basically reasonable, I think? Large linter diff is kinda distracting on a PR like this, I am highly tempted to offer to split those off to a separate commit or yeet those parts of the diff if you don't mind. I could force push the branch even?

EDIT: If I am reading correctly, spec/runners/jasmine1-test-runner.js may be only whitespace changes, it should be fairly easy to exclude that file from the commit. I can easily offer to do that much at least.

EDIT 2: Of course, there's the require('jasmine-focused');. Anyhow, I can offer to split those changes to their own commit.

Feel free if you think it's worthwhile. (I swear I'm not doing it on purpose; it's just how linter-eslint works with our root .eslintrc — saving means autofixing. Often I don't even realize it's happened.)

[DeeDeeG]

Sorry for the delay, looks good to me, and it's good to not allow a lot of tests to be subtly (and likely accidentally) disabled by focusing just one or two tests and failing to un-focus them!