fix(transactions): add ConflictingNonceInMempool to TxRejectedReason …

[Wutche]

Description

Adds the missing ConflictingNonceInMempool error type to the TxRejectedReason enum and the corresponding ConflictingNonceInMempoolRejection type to TxBroadcastResultRejected.

This error can be returned by Stacks nodes when broadcasting a transaction that has a conflicting nonce with another transaction already in the mempool.

Changes:

• Added ConflictingNonceInMempool to TxRejectedReason enum in constants.ts
• Added ConflictingNonceInMempoolRejection type in types.ts
• Added the new type to TxBroadcastResultRejected union

Closes #1801

Breaking change?

None - this is purely additive.

@janniks @zone117x

Example

import { TxRejectedReason, ConflictingNonceInMempoolRejection } from '@stacks/transactions';

// Now developers can properly handle this rejection type
if (result.reason === TxRejectedReason.ConflictingNonceInMempool) {
  console.log(`Nonce conflict: expected ${result.reason_data.expected}, got ${result.reason_data.actual}`);
}

Checklist

• Unit tested updated code paths
• Tagged 1 of @janniks or @zone117x for review

[friedger]

There is no such field like expected and actual. See https://github.com/stacks-network/stacks-core/blob/e6c240e0c0dc763b1cff8fd5fca7b4c237da8bdb/stackslib/src/core/mempool.rs#L2217C24-L2217C40

[Wutche]

alright

[Wutche]

@friedger still waiting for your review