Clients that don't advertise the `exchange_exchange_bindings` capability can't have connections listed.

[lukebakken]

https://github.com/michaelklishin/rabbitmq-http-api-rs/blob/main/src/responses.rs#L584-L585

Repro steps:

• Start a client that doesn't advertise exchange_exchange_bindings (like Pika)
• Try to list connections using rabbitmqadmin-ng connections list
• This is the error (screenshot, because coping an ASCII table isn't working right now):

This is due to ClientCapabilities requiring exchange_exchange_bindings to be present in the JSON response. I don't think we can expect any specific capability to be present.

I'll see if I can figure out a fix! I will ensure Pika sends the exchange_exchange_bindings capability in the next release.

Originally found by @tomtaoran

[michaelklishin]

@lukebakken the fix should be a matter of making this capability an Option<bool> in this struct.

Here's an example you can follow: https://github.com/michaelklishin/rabbitmq-http-api-rs/blob/main/src/responses.rs#L2060-L2061.

[michaelklishin]

I guess we can make all capabilities that might be missing optional but they haven't changed in such a long time that it's a rare thing to see.

[lukebakken]

Thanks!