Bump net-did 2.0.1 → 2.2.0 and NetCrypto 1.1.0 → 1.1.0 (downstream convergence for net-wallet-sdk 0.2.0)

[moisesja]

Summary

Please bump this library's foundation pins:

• NetDid.* (NetDid.Core, NetDid.Extensions.DependencyInjection, NetDid.Method.Key)
  2.0.1 → 2.2.0
• NetCrypto 1.1.0 → 1.2.0

(NetCid stays 1.6.0.) Both are published on nuget.org.

Why (downstream convergence for net-wallet-sdk 0.2.0)

net-wallet-sdk 0.2.0 ships an identity document-update / key-rotation integrity contract (FR-ID-10)
that depends on net-did 2.2.0's DidUpdateResult evidence — AuthorizationChange (net-did#82)
plus the key-specific UpdateKeyChange / EffectiveUpdateKeys (net-did#91). Those default to
Unknown / null on older net-did drivers, and net-wallet-sdk then fails closed by design
(DocumentUpdateNotDocumentOnlyException / IdentityRotationNoKeyChangeException,
Reported = Unknown).

A wallet consumer that also references Credentials.* pulls this library's net-did pins into the
transitive graph. While Credentials.* declares net-did 2.0.1, the resolved graph converges on
net-did 2.2.0 / NetCrypto 1.2.0 only once every foundation library moves up. (Tracked from
net-wallet-sdk PR #15 round-4 review, item 5.)

Current declarations (Directory.Packages.props)

• NetDid.Core / NetDid.Extensions.DependencyInjection / NetDid.Method.Key — all 2.0.1
• NetCrypto 1.1.0, NetCid 1.6.0

Compatibility

• net-did 2.2.0 is additive over 2.0.1 for the surfaces Credentials uses (resolution, did:key): the
  new DidUpdateResult members are nullable additions. The 2.1→2.2 line tightened the did:webvh
  Update/Deactivate driver and carries did:webvh conformance fixes — only relevant if this library
  exercises webvh update/deactivate.
• NetCrypto 1.1.0 → 1.2.0: verify no NU1605 downgrade (Credentials sits on
  DataProofsDotnet.{Core,Jose,Cose} 1.1.0 + NetCrypto — confirm the graph still resolves).

Acceptance

• Bump the two pins; dotnet restore --locked-mode clean (regenerate packages.lock.json); full
  suite green; publish new Credentials.* releases.