Upgrade @pkcprotocol/pkc-js from 0.0.99 to 0.0.101

[tomcasaburi]

Goal

Bump @pkcprotocol/pkc-js from 0.0.99 to 0.0.101, the latest on npm.

Notable upstream changes since 0.0.99

• 0.0.100: duplicate challenge deliveries are dropped and a second challenge answer is rejected (fix(publication): drop duplicate challenge deliveries and reject a second challenge answer (#349) pkcprotocol/pkc-js#350). Gateway polls are paced on max-age, If-None-Match is fixed, and records are published with a 20s TTL (perf(community): pace gateway polls on max-age, fix If-None-Match, publish 20s record ttl pkcprotocol/pkc-js#338).
• 0.0.101: challenge excludes, roles and address lists are bound to the signer (fix(community): bind excludes, roles and address lists to the signer and drop exclude.address pkcprotocol/pkc-js#294). exclude.address is removed and replaced by exclude.publicKeys / exclude.names. exclude.role is renamed to exclude.roles. Community settings that still use either old field are rejected (ERR_CHALLENGE_EXCLUDE_ROLE_FIELD_RENAMED for role). DB_VERSION goes from 41 to 42 and migrates stored settings to the new fields.

Why now

5chan-board-manager's default preset is moving to exclude.roles (bitsocialnet/5chan-board-manager#11). On a node running pkc-js 0.0.99, that key is accepted but ignored, so moderators lose their challenge exemption until bitsocial-cli ships pkc-js >= 0.0.101.

Plan

1. npm install --save-exact @pkcprotocol/pkc-js@0.0.101
2. npm run build && npm run build:test
3. npm run test:cli
4. Fix any CLI breakage the tests surface
5. Open a PR with Closes #N

[tomcasaburi]

Done in #149. Installed 0.0.101 with --save-exact; no CLI code changes were needed. npm run build && npm run build:test pass, and npm run test:cli passes (44 files, 342 tests passed, 1 skipped).