Remote worker activation fails with the newly created RabbitMQ broker

[marktwtn]

If the RabbitMQ broker is newly created and the remote interface initialization is never called, the remote worker can not be activated successfully.
It prints out the message:

Set the consuming queue: server channel error 404,
message: NOT_FOUND - no queue 'incoming_queue' in vhost '/'

It shows that the corresponding queue does not exist.
In the current implementation, the queue is only declared in the remote interface initialization steps instead of declaring in the remote worker.
Once the initialization is called, the durable queue would exist even if the RabbitMQ broker is restarted.

To solve the problem, the queue should be declared in the remote worker, too.
Repeated declaration would be fine based on the description from the RabbitMQ website:

Before a queue can be used it has to be declared.
Declaring a queue will cause it to be created if it does not already exist.
The declaration will have no effect if the queue does already exist
and its attributes are the same as those in the declaration.