Provide a support for delete queue query parameters

[kubamarchwicki]

The RabbitMQ HTTP API support additional query parameters when deleting a queue. The http-client currently doesn't support it

When DELETEing a queue you can add the query string parameters if-empty=true and / or if-unused=true. These prevent the delete from succeeding if the queue contains messages, or has consumers, respectively

I'll work on that PR

[kubamarchwicki]

That would fix (or open a way to support) #118, isn't it?

[michaelklishin]

#118 may depend on query parameters but is otherwise not really related. Why?

[kubamarchwicki]

I was referring to the query parameters aspect. Sorry if that brought some confusion :)

To my understanding of the codebase, the query parameters are not really used so far in the http-client (or at least I haven't found anything). There is no convention for the model (ShovelInfo, QueueInfo and other *Info classes are used to pass http body details. The *Details classes encapsulate the response data. There are no model classes for query parameters). Additionally, the rest template configuration (I started with the synchronous client) handles path segments and not query parameters.
Building a convention in one of these two changes - will make the other a fairly trivial change.

[michaelklishin]

That's a fair analysis.

[acogoluegnes]

I would add a new deleteQueue(String vhost, String name, DeleteQueueParameters parameters) method with the 2 flags as properties. The parameters would be added to the URL if they're present and the RestTemplate would encode the values with one of the delete methods that accept parameters.

[kubamarchwicki]

Thank you @acogoluegnes - that's exactly how I started. I'll adjust the naming and provide a needed test