[bug]: `AddInvoice`: give a more specific error than `could not create any quotes for the invoice`

[ZZiigguurraatt]

I try to create an invoice when all 4 connected edge nodes have a price that is outside of the range of

taproot-assets.experimental.rfq.acceptpricedeviationppm

and I get could not create any quotes for the invoice as an error response from the gRPC call.

I would expect a more specific error message saying that

taproot-assets.experimental.rfq.acceptpricedeviationppm

was not satisfied AND that it tried with 4 connected edge nodes.

This error message is unclear why no quotes could be created. Were all peers just offline? I have no idea from the message.

[ZZiigguurraatt]

I also get this vague error if my price oracle does not support the group_key that I am trying to get the invoice for if I try to specify the amount in terms of assets. For example

deeb4d7a887f:/$ litcli ln addinvoice --group_key 03cf7ebb7abf0976c52290177fd08ad8ddefb7c7fb6a20ef4df8471f89792b156f --asset_amount 35400
[litcli] error adding invoice: rpc error: code = Unknown desc = could not create any quotes for the invoice
deeb4d7a887f:/$ 

HOWEVER, if I try to specify the amount in sat or msat when my price oracle does not support the group_key that I am trying to get an invoice for, it does give me a useful message

deeb4d7a887f:/$ litcli ln addinvoice --group_key 03cf7ebb7abf0976c52290177fd08ad8ddefb7c7fb6a20ef4df8471f89792b156f --amt_msat 360000
[litcli] error adding invoice: rpc error: code = Unknown desc = error calculating asset max amount: cannot query oracle: OracleError(code=0, msg=Unsupported subject asset)
deeb4d7a887f:/$ 
deeb4d7a887f:/$ 
deeb4d7a887f:/$ litcli ln addinvoice --group_key 03cf7ebb7abf0976c52290177fd08ad8ddefb7c7fb6a20ef4df8471f89792b156f --amt 360
[litcli] error adding invoice: rpc error: code = Unknown desc = error calculating asset max amount: cannot query oracle: OracleError(code=0, msg=Unsupported subject asset)
deeb4d7a887f:/$ 

In these examples, I'm trying to do it from a "wallet node" that only has a single channel, so I'm not doing multi-RFQ here like I was in the original issue description.