Use named import for fast-json-patch update to 2.2.0

[tomalec]

Description

• Changed default import to named import for fast-json-patch
• Updated fast-json-patch back to the current 2.2.0

Motivation and Context

As reported at Starcounter-Jack/JSON-Patch#233 and #1460 (Fixes #1460) there was a problem initializing Swagger with latest fast-json-patch. It occurred to be related to backward incompatible change related to undocumented default export. We will revert this change, and release a new version to support this and many other projects that are currently using import jsonPatch from 'fast-json-patch'.

However, we recommend to use named or star imports:

import { applyPatch } from 'fast-json-patch'
import * as jsonPatch from `fast-json-patch'

Those worked with old versions, works fine with 2.2.0, and we plan long term support for such import.
So you can use it with current versions without a need to wait for our fix.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• No code changes (changes to documentation, CI, metadata, etc)
• Dependency changes (any modification to dependencies in package.json)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project. - at least I hope so, I haven't found any guidelines, nor CONTRIBUTING.md
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed. - I tried running npm test locally, but they were failing even on master :(

[tim-lai]

@tomalec Thanks for the PR! It's been awhile, but can you rebase, resolve merge conflicts, and apply suggestions. One is a lint error. Once done, this PR will be merged.

[tomalec]

@tim-lai thanks for the review.
All comments addressed.

[tim-lai]

@tomalec please resolve merge conflicts as well. Thanks!

[char0n]

@tomalec thank you for reporting this! Closing this PR in favor of #1564