Update deps for spelling tool

[xirzec]

To resolve some scan issues with old transitive deps.

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[weshaggard]

@danieljurek how much risk do you think we have here?

[danieljurek]

I think this is OK to merge now as the mitigation for new spelling error detections is unchanged: If your PR is blocked, update the word list or fix your spelling errors.

Upgrading the whole of cspell at once is the right way to do this instead of a subset of cspell's dependencies.

I would rate this as relatively low risk because we've updated cspell in the past in response to problems and it hasn't resulted in catastrophic failures.

The failures I'd be concerned about when doing this are:

1. Changes to the CLI interface that mean we need to update our scripts that call cspell (either with output parsing or CLI parameters) ... but the SemVer doesn't suggest any large breaks (assuming SemVer is used correctly in this context)
2. Changes in the detection logic which result in a lot of new spelling errors. Off the top of my head, this can come from changes in how word boundaries are determined or elimination or refactoring of dictionary terms. This would be treated as any new spelling error detection: Update word list or fix spelling error in source.

Detailed testing of this change would have to be done on a per-repo basis as different languages scan at different levels of granularity: https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/367/Capabilities-and-State

[weshaggard]

Thanks @xirzec for starting this PR I took it through the sync process.