Use mocha 10

[aljones15]

Addresses: #23

To Do

• look for potential changes in the API for Mocha class

[mattcollier]

Thanks for picking this up @aljones15

[davidlehn]

Unless there's a special reason, we can probably leave finding changelogs as an exercise for the reader.

Suggested change

	- **BREAKING**: Upgraded to mocha 10. [See mocha 10's changelog](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md)
	- **BREAKING**: Update to `mocha@10`.

[aljones15]

Not as sure on this one, the major reason for the breaking release is the upgrade to mocha 10 so I think we should link to their change log.

[davidlehn]

Sure, it's just a hassle to do in general. Maybe link direct to v10 section: https://github.com/mochajs/mocha/blob/master/CHANGELOG.md#1000--2022-05-01.

[mattcollier]

Fixed.

[mattcollier]

@davidlehn @aljones15 @dlongley I just tested this with mocha@10 on a few bedrock libs bedrock-tokenizer, bedrock-tokenization and bedrock-vc-issuer. Everything seems to just work, which makes sense because there are no breaking changes to the mocha API surface (according to the changelog) that impact Bedrock devs.

As for the Node >= 14 requirement constituting a breaking change.

Bedrock core started requiring node 14+ over a year ago in v5: https://github.com/digitalbazaar/bedrock/blob/main/CHANGELOG.md#500---2022-03-31

This lib (bedrock-test) has a peer dep requirement of @bedrock/core@6 already which makes the Node 14+ requirement implicit.

I propose that this mocha update be released as a minor release to avoid having to touch the nearly 60 libs that use it. Any objections?

[davidlehn]

Minor release is ok with me.

[dlongley]

I'm fine with a minor release based on @mattcollier's comments.