Also, correct the change logs to be much more consistent between each
other and ensure the ospec and stream change logs are linked to from
Mithril's primary change log.
* feat(ospec): CLI support for file-patterns and an --ignore flag
The added dependency is only used by the node.js binary - which normally only ever installed via npm/yarn anyway.
This does not interfer with ospec proper being dependencyless.
* chore(mithril): Add glob dependency needed by the ospec binary
this is only needed while ospec is inlined in the
mithril repo. As soon as ospec is split away into a
standalone npm module, this will not be required anymore.
* refactor(ospec): Use 'match' events instead of callback
Performance should be similar, but the code looks
cleaner and easier to grok.
* Misc tweaks
Getting set up with ospec is deceptively simple, and adding just a bit
more documentation should help new users from falling into the trap of
overthinking the test config. (I know that I ended up down a very
strange rabbit hole when pulling ospec into a project).
This also adjusts the bin definition in the package file so that we can
hopefully just use the `ospec` command instead of a folder ref.
