pcli tx lp order sell gives a mispriced position when used with delegation tokens

[hdevalence]

To Reproduce

Create a position selling one delegation token for another at a 1:1 price:

cargo run --release --bin pcli -- tx lp order sell 49925.817225delegation_penumbravalid14mznnxs03r0sqkwrq7mvnjwdwufn7cu29gu4hpnwcn4u7mgqqcpsvhe7h9@1delegation_penumbravalid1cqwaxsxjmj4hl78t906gtf5gcfhkpu80ju3zjtkdppelx8g5qcxqgas4lg/25bps

The position has a price off by a factor of 1,000,000:

 ID          plpid1ta9emmcxq9gvdfs299mk8gjc03rlwkxv4jme2f46uamaee294khszramt7
 State       opened
 Reserves 1  0delegation_penumbravalid1cqwaxsxjmj4hl78t906gtf5gcfhkpu80ju3zjtkdppelx8g5qcxqgas4lg
 Reserves 2  49925.817225delegation_penumbravalid14mznnxs03r0sqkwrq7mvnjwdwufn7cu29gu4hpnwcn4u7mgqqcpsvhe7h9
 Fee         25bps
 p           49925817225
 q           49925817225000000
 Nonce       de3282fdaedcb9760a77bdf786e5072b67845183b95a3684316abb98907fdcd0

Expected behavior
p and q should be identical, since the price is supposed to be 1.

[hdevalence]

I think this is probably related to denom metadata issues?

[hdevalence]

Added some debug statements:

2023-05-18T19:22:35.693161Z DEBUG penumbra_crypto::dex::lp::order: parsed sell order offered_unit=delegation_penumbravalid offered=Value { amount: 1234000000, asset_id: passet1tg55dqdtvwhcmfmr7jk0sjzaqfhxwxv6juhp6zlf74djdp34vczq7pwtn9 } price=Value { amount: 1000000, asset_id: passet1jg66mgvzdafh0v5dulhtj4p23a5xklw43zaarl6plyyv5vepxqrs5y79vh }
2023-05-18T19:22:35.693192Z DEBUG penumbra_crypto::dex::lp::order: computed desired amount price_amount=1000000 offered_amount=1234000000 offered_unit_amount=1 desired_amount=1234000000000000
2023-05-18T19:22:35.693197Z DEBUG penumbra_crypto::dex::lp::order: computed p and q p=1234000000000000 q=1234000000

Looks like the desired_amount is wrong.

[hdevalence]

The offered_unit was truncated because of a bad regex, which discarded the validator ID part of the delegation token denom. The bad denom was not noticed because our asset registry silently invents new assets on unknown denoms; fixing that would have prevented the bug.