chore: bump version to 3.0.0 to reflect breaking change

BREAKING CHANGE: All KMS_* environment variables were renamed to
KEY_PROVIDER_* in PR #195. Any deployment using the old variable names
will break without a config update:

  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

This was missed in the prior semver bump (2.1.0 -> 2.1.1). Correcting
to 3.0.0 per semver convention.

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

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",