fix(soroban): add strict option to reject with ConfirmationTimeoutError on timeout (closes #596)

[Ranjeet2063]

Summary

Adds an opt-in { strict: true } option to ConfirmationPollingOptions so callers can distinguish a confirmed transaction from an unconfirmed or timed-out submission via a typed ConfirmationTimeoutError (closes #596).

Changes

• src/errors.ts:
  • Added ConfirmationTimeoutError carrying hash, attempts, and timeoutMs.
  • Registered ConfirmationTimeoutError in isConduitError().
• src/soroban.ts:
  • Added strict?: boolean to ConfirmationPollingOptions and normalized defaults.
  • In invokeContract(), when strict: true and polling exceeds maxAttempts without SUCCESS/FAILED (or encounters network polling failure), throws ConfirmationTimeoutError.
  • Fully backward compatible: default non-strict mode continues to resolve unconfirmed hash as pending.
• src/index.ts:
  • Re-exported ConfirmationTimeoutError.
• src/tests/invoke-contract-confirmation-timeout.test.ts:
  • 6/6 unit tests covering timeout rejection, success resolution, failure rejection, network error handling, and type-guard recognition.

Verification

• 6/6 unit tests passing.
• Clean typecheck (tsc --noEmit).
• Zero ESLint errors.
• Successful production ESM/CJS build with Rollup.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.