stamper overrides

[moeodeh3]

Summary & Motivation

this pr is a continuation of 1158

the problem we’re trying to solve here is that we have several internal stampers that are configured at provider initialization time, but in some cases we need to be able to update them at runtime

This PR introduces:

• overrideApiKeyStamper()
• overridePasskeyStamper()
  to address that issue

Question: why didn’t we also include a walletStamper override?
the reason is that this gets significantly more complex - especially with WalletConnect -and isn’t currently possible to do without re-initializing the provider, which is fairly expensive. I’m also concerned about potential race conditions here. For now, I’m intentionally excluding this from the pr until a customer explicitly asks for it

as a bonus, this pr also adds:

• deleteApiKeyPair()
  this is useful for teams handling auth themselves and using ephemeral keys (e.g. one-tap passkeys)

How I Tested These Changes

Did you add a changeset?

If updating one of our packages, you'll likely need to add a changeset to your PR. To do so, run pnpm changeset. pnpm changeset will generate a file where you should write a human friendly message about the changes. Note how this (example) includes the package name (should be auto added by the command) along with the type of semver change (major.minor.patch) (which you should set).

These changes will be used at release time to determine what packages to publish and how to bump their version. For more context see this comment.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit fac7565:

Sandbox	Source
@turnkey/example-react-components	Configuration