[Bug] find_lost_did Bad Bytes initializer (versions 2.0.0 -> main)

[BrandtH22]

What happened?

Steps to reproduce:

1. create a wallet in pawket
2. create a did in pawket
3. click on the wallet fingerprint in pawket to reveal the 24 word mnemonic and import it into the chia reference client

NOTE - the did will be present in the pawket app but not in the chia client
Side note - the sage wallet is able to import the same mnemonics and use the DID without issue

4. run the find_lost_did command on the newly created DID
5. review the errors

When running the find lost did command on a did that is created in pawket (note it could be other dids also but this is a reproducible method to expose this issue) the chia client fails to find the did and returns an error of (note this same error is present in the debug log file)

Failed to find lost DID: RPC response failure: {"error": "bad bytes32 initializer b''", "success": false, "traceback": "Traceback (most recent call last):\n  File \"chia/rpc/util.py\", line 84, in inner\n  File \"chia/rpc/wallet_rpc_api.py\", line 2545, in did_find_lost_did\n  File \"chia_rs/sized_byte_class.py\", line 46, in __init__\nValueError: bad bytes32 initializer b''\n"}

When attempting the same command on main this error is duplicated:

Failed to find lost DID: RPC response failure: {"error": "bad bytes32 initializer b''", "success": false, "traceback": "Traceback (most recent call last):\n  File \"/Users/USERNAME/chia-blockchain/chia/rpc/util.py\", line 84, in inner\n    res_object = await f(request_data)\n                 ^^^^^^^^^^^^^^^^^^^^^\n  File \"/Users/USERNAME/chia-blockchain/chia/rpc/wallet_rpc_api.py\", line 2545, in did_find_lost_did\n    bytes32(recovery_list_hash.as_atom()),\n    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n  File \"/Users/brandtholmes/chia-blockchain/.venv/lib/python3.12/site-packages/chia_rs/sized_byte_class.py\", line 46, in __init__\n    raise ValueError(f\"bad {type(self).__name__} initializer {v}\")\nValueError: bad bytes32 initializer b''\n"}

Version

2.4.4

What platform are you using?

macOS

What ui mode are you using?

CLI

Relevant log output

No response

[Rigidity]

The cause of the issue is that the recovery list hash can be null on-chain but the reference wallet doesn't allow this. Both Pawket and Sage default to a null recovery list hash since it's 32 bytes cheaper to reveal on-chain every spend.