Usage of "m/" in derivation path #2671
Description
In #2451 we removed the ability to parse derivation paths that include the leading 'm'. While testing the rc1 I attempted to upgrade bitcoind which includes an RPC call to getaddressinfo which returns the following JSON. As can be seen the derivation path includes the 'm'. This means our current release candidate is unable to parse JSON returned by Bitcoin Core, surely that is a bug?
TRACE][bitcoincore_rpc]: JSON-RPC response for getaddressinfo:
{
"address":"n1fg6HFS7TV7ETSvCWD68k6ZNEsXYWg88U",
"scriptPubKey":"76a914dd08bbd7d4526a708aa9346a50918c411a860d7388ac",
"ismine":true,
"solvable":true,
"desc":"pkh([5041878d/0'/0'/6']033c9bfc9acc37f679ac7099fc0eda080efca7b454a35818f8fd9d11a79245c725)#5p87z2p4",
"iswatchonly":false,
"isscript":false,
"iswitness":false,
"pubkey":"033c9bfc9acc37f679ac7099fc0eda080efca7b454a35818f8fd9d11a79245c725",
"iscompressed":true,
"ischange":false,
"timestamp":1712535496,
"hdkeypath":"m/0'/0'/6'",
"hdseedid":"0510f7177cb0e3f37c22b27d222befe4e797bcc5",
"hdmasterfingerprint":"5041878d",
"labels":[""]
}