v1.1.2: align with vc-vault-factory v0.4.0 + did:stellar

Aligns the SDK (@acta-team/credentials) with the v0.4.0 API (factory + single-tenant vaults) and did:stellar issuance. The SDK is a thin client and the API derives each owner's vault, so the surface changes are focused.

Added

• Issuer deny-list (deny-by-exception; issuance is open by default):
  • client.vaultDenyIssuer(...) for POST /contracts/vault/deny-issuer
  • client.vaultAllowIssuer(...) for POST /contracts/vault/allow-issuer
  • useVault().denyIssuer(...) / allowIssuer(...)
• Optional userSalt on createVault, issue, revoke, and the deny/allow helpers (selects which deterministic vault to target).
• getContractVersion({ owner }) for a per-vault version.
• ConfigResponse now surfaces factoryContractId, networkType, vaultWasmHash, didStellarRegistryId (actaContractId kept as an alias).

Fixed

• useCredential().revoke(...) now sends owner. The v0.4.0 API needs it to derive the single-tenant vault; without it, revocation could not resolve a vault.

Changed

• useVault().authorizeIssuer / revokeIssuer keep working but now map to the API's allow-issuer / deny-issuer aliases. Prefer allowIssuer / denyIssuer.
• Issuance requires a resolvable did:stellar issuer whose controller matches the signer (enforced by the API). useCredential().issue auto-resolves the issuer DID via getOrCreateIssuerIdentity when omitted.

Removed (breaking)

• client.vcIssueLinked and useCredential().issueLinked (linked credentials).
• client.vaultGetVcParent and useVaultRead().getVcParent.

Compatibility

• Requires acta-api v1.1.1.

Verification

• npm run build (tsup ESM/CJS + DTS/typecheck) passes.