Add missing docker configurations

[ajharry69]

What is being delivered?

1. Added a Dockerfile for use in docker-compose.yaml file.
2. Removed reference to non-existent Dockerfile in the docker-compose.yaml file build context.
3. Add Make targets for conveniently running integration tests for both RabbitMQ and ActiveMQ.
4. Decouple STOMP server host user from local environment by retrieving the host from settings.STOMP_SERVER_HOST.

What impacts?

With these changes, running tests and lint checks as configured in the docker-compose.yaml becomes is possible without manually installing dependencies in your local development environment. You simply run make test and let docker (compose) do the rest.

[ricardochaves]

Port 61613 is used inside the code. The pipeline probably broke because of this. Do you really need to change the port?
The idea would be to start one container at a time and not both at the same time.
Did this configuration work locally?

[ajharry69]

I started all the services at the same time (using docker compose up [--build]), hence the reason it was reporting a port already in use error. I can:

1. revert the change and leave clear guidelines on the README about how to run the tests in docker compose setup, OR
2. change the rabbitmq port in the code to support both cases.

I am not sure how detrimental the 2nd option will be, but a person new to the repo like I am will expect it not to fail if they ran the same command.

[fabiohk]

There's this section that says to run the tests with either broker-activemq or broker-rabbitmq. If it's not clear enough, it's an opportunity to improve it

[ajharry69]

There's this section that says to run the tests with either broker-activemq or broker-rabbitmq. If it's not clear enough, it's an opportunity to improve it

I'll have a closer look at how to better approach this, then update ASAP.

[ajharry69]

@ricardochaves , I am not sure why the pipeline is still failing despite rolling back the port change. I successfully ran tox in my local setup as per the documentation. Checking the Azure pipeline reports seems to require privileged access, or I may not be going about it correctly.