chore(deps): upgrade decode-uri-component to >= 0.2.2

[charellesandig]

Fixes #2243

Depends on: https://github.com/hyperledger/cacti/issues/2357

Signed-off-by: charellesandig charelle.wrk@gmail.com

[jagpreetsinghsasan]

LGTM

[petermetz]

@charellesandig Please upgrade all occurrences of the problematic version of the dependency not just one.

$ npm ls decode-uri-component
@hyperledger/cactus@ /home/peter/a/blockchain/cactus
├─┬ @hyperledger/cactus-cmd-socketio-server@1.1.3 -> ./packages/cactus-cmd-socketio-server
│ └─┬ web3@1.8.2
│   └─┬ web3-bzz@1.8.2
│     └─┬ swarm-js@0.1.40
│       └─┬ xhr-request@1.1.0
│         └─┬ query-string@5.1.1
│           └── decode-uri-component@0.2.2 deduped
├─┬ @hyperledger/cactus-example-supply-chain-frontend@1.1.3 -> ./examples/cactus-example-supply-chain-frontend
│ └─┬ @angular-devkit/build-angular@13.3.5
│   └─┬ stylus@0.56.0
│     └─┬ css@3.0.0
│       └─┬ source-map-resolve@0.6.0
│         └── decode-uri-component@0.2.2 deduped
└─┬ @hyperledger/cactus-test-tooling@1.1.3 -> ./packages/cactus-test-tooling
  └─┬ keycloak-admin@1.14.22
    └─┬ query-string@6.14.1
      └── decode-uri-component@0.2.2

[charellesandig]

Hi @petermetz , for these packages I upgraded the direct dependencies where decode-uri-component occurs.

cactus-cmd-socketio-server
cactus-example-carbon-accounting-frontend
cactus-test-tooling
cactus-verifier-client

For cactus-verifier-client when I upgraded from "jest-extended": "0.11.5" to "jest-extended": "3.0.1" the docode-uri-component is not present anymore.

[petermetz]

@charellesandig Please see https://github.com/hyperledger/cacti/pull/2296#discussion_r1163124456
Once the dependency has been resolved (e.g. that other issue fixed) then please do the webpack build test again to see if it passes or not. If it does, then just re-request my review and we'll be good to go)

[charellesandig]

Depends on: #2357

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

<sup><sub>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sub></sup>

[petermetz]

LGTM

[petermetz]

Can't merge until maintainer consensus has been achieved.

[petermetz]

I rebased onto upstream/main, fixed the merge conflicts and in the meantime Izuru reviewed it too, so we are good to go.