Fix failing spec

[savetheclocktower]

No clue how this got through CI on the PR branch, but a spec is failing now solely because it is not inheriting a default value from a configuration. All that's needed is to explicitly set the defaults in the test, so that's what I've done.

[savetheclocktower]

Check that — the defaults needed to be set explicitly because the language-javascript package hadn't been activated, so none of the defaults were applied in the first place. This confirms that the test failure is entirely a case of developer error when writing specs. The developer is me. I am that person.

[DeeDeeG]

Why is our CI like this?

How did this only fail on master branch?? 🤔

(I'd be more surprised to get an actual answer than not at this point, TBH. "CI mysteries" is easily believable. Some specific yet explainable voodoo seems more far-fetched.)

[savetheclocktower]

It was failing for me locally, too, once I checked. Sigh.