[BUG] Coinbase Notification Type Detection, Spend Permission Grant, and Passkey Sign-In Failure

[joe10832]

Bug Description

Coinbase Notification Type Detection Logic, Spend Permission Grant, and Hardcoded Passkey Credential sign-in are not functioning as expected in Onchain Test Kit (OTK-30).

Steps to Reproduce

1. Prepare Onchain Test Kit and configure for Coinbase Wallet usage
2. Initiate a workflow that triggers notification type detection
3. Attempt to grant spend permission using hardcoded passkey
4. Try to sign in with hardcoded passkey credential

Expected Behavior

Notification type should be detected correctly, spend permission should be granted, and sign in with hardcoded passkey should succeed without errors.

Actual Behavior

Notification type is not detected; spend permission cannot be granted; sign in with hardcoded passkey credential fails. Observed error during workflow execution.

Environment Information

• Onchain Test Kit Version: [please supply]
• Node.js Version: [please supply]
• Operating System: [please supply]
• Browser: [please supply]
• Wallet: Coinbase Wallet

Configuration Used

// Paste your configuration code here
// Example:
const config = configure()
  .withCoinbaseWallet()
  // ... other configuration for notification type and passkey
  .build();

Error Logs

Error encountered during notification detection and passkey sign-in (see linked PR review).
_Originally posted by @joe10832 in https://github.com/MunyayLLC/https-github.com-joe10832-onchaintestkit/pull/197#pullrequestreview-3307872186_

Code Sample

import { createOnchainTest, configure } from '@coinbase/onchaintestkit';

const test = createOnchainTest(/* your config */);

test('coinbase notification test', async ({ page, coinbase }) => {
  // Steps that cause the bug
});

Screenshots

N/A

Additional Context

Issue discovered while implementing OTK-30. Test failure relates to Coinbase-specific logic for notification, spend permission, and passkey credential sign-in.

Possible Solution

Review and correct the Coinbase notification detection logic, permission grant flow, and passkey credential handling in OTK.

Checklist

• I have searched for existing issues that describe this bug
• I have included all the required environment information
• I have provided a minimal code example that reproduces the issue
• I have included relevant error messages and logs