Fixing broken test in the CLI

[alegomes]

Description

The build process was failing on my local environment. The reason was a failing unit test.

> Task :waltid-applications:waltid-cli:jvmTest

WaltIdDidCreateCmdTest[jvm] > should succeed creating a DID key using jwk_jcs-pub with all key types()[jvm] FAILED
    org.opentest4j.AssertionFailedError at WaltIdDidCreateCmdTest.kt:197

Type of Change

• [ x ] bug fix - change which fixes an issue
• [ ] new feature - change which adds functionality

Checklist

• [ x ] code cleanup and self-review
• [ x ] unit + e2e test coverage
• [ x ] documentation updated accordingly

Breaking

No.

• -

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[alegomes]

Maybe, because you don't have white spaces on your PATH, @mikeplotean ?