fix: `@schematics/update` vulnerabilities (#836)

[acn-masatadakurihara]

• fix: npm report @schematics/update high severity vulnerabilitie.

  @datorama/akita:7.1.1 > "schematics-utilities": "^2.0.3" > @schematics/update@0.803.29 (deprecated) > "ini" : 1.3.5

Create schematics-utilities-fix with @schematics/update references removed from schematics-utilities, and fix Akita dependency packages from schematics-utilities to schematics- utilities-fix.

PR Checklist

Please check if your PR fulfills the following requirements:

• [x] The commit message follows our guidelines: https://github.com/datorama/akita/blob/master/CONTRIBUTING.md#commit
• [x] Tests for the changes have been added (for bug fixes / features)
• [x] Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Npm report high severity vulnerabilitie @datorama/akita:7.1.1 > "schematics-utilities": "^2.0.3" > @schematics/update@0.803.29 (deprecated) > "ini" : 1.3.5

Issue Number: https://github.com/salesforce/akita/issues/836

What is the new behavior?

Create schematics-utilities-fix with @schematics/update references removed from schematics-utilities, and fix Akita dependency packages from schematics-utilities to schematics- utilities-fix.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[salesforce-cla[bot]]

Thanks for the contribution! Before we can merge this, we need @masatada-kurihara to sign the Salesforce.com Contributor License Agreement.

[swierzbicki]

How long will we wait for this contribution? 🤔

[scubafly]

Looks like the build failed. ( akita@0.0.0 build:all /home/runner/work/akita/akita ) should there not be a version number instead of 0.0.0 ?