Resolve @pezkuwi/scure-sr25519 from npm, not a path on one machine

The root resolutions pointed @pezkuwi/scure-sr25519 at
portal:/home/mamostehp/pezkuwi-wasm/packages/scure-sr25519, a directory
that only existed on the machine 14.0.25 was published from. Everywhere
else `yarn install` stops with "Manifest not found", so this repository
could not be installed, built or tested, and the PR workflow had never run.

util-crypto already asks for ^0.2.1, which is on npm; its lib/ is identical
to packages/scure-sr25519 in pezkuwi-wasm (same "bizinikiwi" signing
context). Dropping the resolution resolves it there.

With this, install, lint and test run. They are not green yet: 161 of
3014 tests fail, most of them on @pezkuwi/wasm-crypto 7.5.17 stubs
(secp256k1, ed25519, scrypt, bip39Generate "not yet implemented"), which
pezkuwi-wasm#2 fixes as 7.5.19. That, the remaining failures and the
continue-on-error in pr-any.yml follow once 7.5.19 is published.

package.json

@@ -43,7 +43,6 @@
   "resolutions": {
     "@pezkuwi/dev": "^0.85.11",
     "@pezkuwi/dev-test": "^0.85.7",
-    "@pezkuwi/scure-sr25519": "portal:/home/mamostehp/pezkuwi-wasm/packages/scure-sr25519",
     "@pezkuwi/wasm-bridge": "7.5.17",
     "@pezkuwi/wasm-crypto": "7.5.17",
     "@pezkuwi/wasm-crypto-asmjs": "7.5.17",