The `dumpwallet` RPC command throws an error at the signet node and stops it.
~~This does not happen in mainnet or testnet, where the command worked successfully in my tests..~~
Originally this error was only happening on signet, but it also happened on testnet after it worked successfully for a while.

**Expected behavior**

The RPC `dumpwallet` command is expected to return a success message and create the dump file that contains the private keys.

**Actual behavior**

The command returns an error on client side (`bitcoin-cli`):
`error: timeout on transient error: Could not connect to the server 127.0.0.1:38332 (error code 1 - "EOF reached")
Make sure the bitcoind server is running and that you are connecting to the correct RPC port.`

And it throws an error at the signet node and stops it.

```
POTENTIAL DEADLOCK DETECTED
Previous lock order was:
  'cs_wallet' in wallet/wallet.cpp:2860 (in thread 'httpworker.1')
  (2) '::cs_main' in node/interfaces.cpp:687 (in thread 'httpworker.1')
  'm_node.mempool->cs' in node/interfaces.cpp:687 (in thread 'httpworker.1')
  'cs_wallet' in wallet/wallet.cpp:1204 (in thread 'httpworker.1')
  (1) 'cs_KeyStore' in script/signingprovider.cpp:165 (in thread 'httpworker.1')
Current lock order is:
  'wallet.cs_wallet' in wallet/rpcdump.cpp:743 (in thread 'httpworker.3')
  (1) 'spk_man.cs_KeyStore' in wallet/rpcdump.cpp:743 (in thread 'httpworker.3')
  (1) 'spk_man->cs_KeyStore' in wallet/wallet.cpp:2303 (in thread 'httpworker.3')
  (2) 'cs_main' in node/interfaces.cpp:493 (in thread 'httpworker.3')
Assertion failed: detected inconsistent lock order for 'cs_main' in node/interfaces.cpp:493 (in thread 'httpworker.3'), details in debug log.
Aborted (core dumped)
```

**To reproduce**

Start the node on signet mode:
`bitcoind -signet`

And dump an existing wallet:
`bitcoin-cli -signet -rpcwallet="legacy_wallet_01" dumpwallet "filename"`

**System information**

The bitcoin node was compiled from master (commit: `df2b5dadfb2dc21b05e5a60b71987fb5b96201f5`)
Ubuntu 20.04, 8 CPUs, 12 GiB RAM and SSD.

int64_t block_time;
        CHECK_NONFATAL(chain().findBlock(entry.second->hashBlock, FoundBlock().time(block_time)));
        mapKeyBirth[entry.first] = block_time - TIMESTAMP_WINDOW; // block times can be 2h off
    }
}
/**
 * Compute smart timestamp for a transaction being added to the waet.
 *
 * Logic:
 * - If sending a transaction, assign its timestamp to the current time.
 * - If receiving a transaction outside a block, assign its timestamp to the
 *   current time.
 * - If receiving a block with a future timestamp, assign a its (not already
 *   known) transactions' timestamps to the current time.
 * - If receiving a block with a past timestamp, before the most recent known
 *   transaction (that we care about), assign a its (not already known)
 *   transactions' timestamps to the same timestamp as that most-recent-known
 *   transaction.
 * - If receiving a block with a past timestamp, but after the most recent known
 *   transaction, assign a its (not already known) transactions' timestamps to
 *   the block time.
 *
 * For more information see CWaetTx::nTimeSmart,
 * https://bitcointalk.org/?topic=54527, or
 * https://github.com/bitcoin/bitcoin/pu/1393.
 */
unsigned int CWaet::ComputeTimeSmart(const CWaetTx& wtx) const