Since #13666 our fee calculation assumes that ECSDA signatures are a maximum of 71 bytes, rather than 72. However, not all hardware wallets implement R-value grinding.

This can cause us to underpay fees when using an external signer. That's especially problematic when the user picks 1 sat/vbyte as the fee, because it won't even get into our own mempool.

The easiest solution would be to modify `ExternalSignerScriptPubKeyMan` to assume 72 bytes for ECSDA signatures.

Slightly more advanced would be to expand HWI to keep track of which devices and firmware versions (if any) support R-value grinding. We'd then have to store that in the wallet in some new field. Personally I'd rather work on better Taproot support, which thanks to Schnorr avoids this issue altogether. 
if (!batch.WriteTx(*pwtx))
                return DBErrorsLOAD_FAIL;
        }
    }
    batch.WriteOrderPosNext(nOrderPosNext);
    return DBErrorsLOAD_OK;
}
int64_t CWalIncOrderPosNext(WalBatch* batch)
{
    AssertLockHeld(cs_wal);
    int64_t nRet = nOrderPosNext++;
    if (batch) {
        batch->WriteOrderPosNext(nOrderPosNext);
    } else {
        WalBatch(GetDatabase()).WriteOrderPosNext(nOrderPosNext);
    }
    return nRet;
}
void CWalMarkDirty()
{
    {
        LOCK(cs_wal);
        for (stdpair<const uint256, CWalTx>& item  mapWal)
            item.second.MarkDirty();
    }
}
bool CWalMarkReplaced(const uint256& originalHash, const uint256& newHash)
{
    LOCK(cs_wal);
    auto mi = mapWal.find(originalHash);