chore!: bump version to 3.0.0 to reflect breaking change

Corrects the version from 2.1.1 to 3.0.0.

PR #195 (refactor: rename KMS to Key Provider) introduced a breaking
change that was not reflected in the semver bump at the time:

  All KMS_* environment variables were renamed to KEY_PROVIDER_*:
    KMS_URL                           -> KEY_PROVIDER_URL
    KMS_SERVER_CA_CERT_PATH           -> KEY_PROVIDER_SERVER_CA_CERT_PATH
    KMS_CLIENT_TLS_KEY_PATH           -> KEY_PROVIDER_CLIENT_TLS_KEY_PATH
    KMS_CLIENT_TLS_CERT_PATH          -> KEY_PROVIDER_CLIENT_TLS_CERT_PATH
    KMS_CLIENT_TLS_KEY                -> KEY_PROVIDER_CLIENT_TLS_KEY
    KMS_CLIENT_TLS_CERT               -> KEY_PROVIDER_CLIENT_TLS_CERT
    KMS_CLIENT_TLS_CA_CERT            -> KEY_PROVIDER_CLIENT_TLS_CA_CERT
    KMS_SERVER_CERT_ALLOW_SELF_SIGNED -> KEY_PROVIDER_SERVER_CERT_ALLOW_SELF_SIGNED

Any deployment using the old KMS_* env vars will break without a config
update. Per semver, a breaking change to the public configuration
interface requires a major version bump.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Ticket: WAL-1481

Author: pranishnepal

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@bitgo/advanced-wallets",
-  "version": "2.1.1",
+  "version": "3.0.0",
   "description": "Advanced Wallets - On-Premises Key Management with BitGo Express",
   "main": "./dist/src/index.js",
   "types": "./dist/src/index.d.ts",