docker compose file and extended documentation

[xai]

As discussed with @kkistm, this PR adds a docker-compose.yml and extends the existing documentation to make running a test environment as easy as possible.

Changes:

• Update @anibalsolon's PR Speed-up development with docker-compose #625 with current versions and build instructions
• Add profiles to the docker-compose.yml to let users decide which services to start in a container:
  • no selection of a profile starts only Postgres and Elasticsearch. This is suited for building and running the openvsx services on the local machine.
  • "openvsx" profile additionally builds and starts all openvsx-related services in separate containers
  • "backend", "frontend", "commandline" profiles for more fine-grained choices.
  • "kibana" profile can optionally be added to explore the Elasticsearch instance more conveniently,
• Add information on how to register example extensions with the local registry.

How to test:

• Run docker compose --profile openvsx up to start Postgres, Elasticsearch, and all three openvsx-related containers (server, webui, cli tools).
• Verify with docker ps that all containers are running.
• Verify that ports 8080 (server) and 3000 (webui) are exposed and that the local deployment works as expected.
• docker compose down (or Ctrl-c in the original shell) for tearing down all containers.

Contributed on behalf of STMicroelectronics

[xai]

For the docker-compose.yml, I changed the restart policy of the elasticsearch and postgres containers.

[amvanbaren]

Hi @xai and @anibalsolon. The PR looks good overall. There's one small change I'd like to request. Can you change marketplace to registry in doc/development.md on line 11 and line 29?

[xai]

Hi @xai and @anibalsolon. The PR looks good overall. There's one small change I'd like to request. Can you change marketplace to registry in doc/development.md on line 11 and line 29?

Sure! I rebased against current master and added a commit to correct our wording.

[amvanbaren]

@xai Alright, can you squash your commits so that this PR can be merged into master as one feature?

[xai]

@xai Alright, can you squash your commits so that this PR can be merged into master as one feature?

Done. I will do the same for my other PRs.