Cover all scenarios through Docker

[Kostov6]

What would you like to be added:
Those are the scenarios we would like to cover:

• Local development
  • provide docforge config (through volume mount) [Docker] Running docforge using docker compose #241
  • provide local manifest (docforge config) [Docker] support local dev #243
  • provide resourceMappings (docforge config and volume mounts) [Docker] support local dev #243
  • exporting website to localhost and browse it through the browser (through port mount) [Docker] Running web server using docker compose #240
• CI/CD
  • consume docforge config (through DOCFORGE_CONFIG) [Docker] Move DOCFORGE_CONFIG in compose instead of image #242
  • export website build result [Docker] Add BUILD_DESTINATION #245

One way to achieve this is through Docker compose

Why is this needed:

• Only the maintenance of the compose files and the Dockerfile will be necessary
• Non-os dependent execution
• Execution of a scenario will only require configuration of a Docker compose file and running docker compose or a normal docker run command

Subtasks:

• [Docker] Running web server using docker compose #240
• [Docker] Running docforge using docker compose #241
• [Docker] Move DOCFORGE_CONFIG in compose instead of image #242
• [Docker] support local dev #243

[dimitar-kostadinov]

The listed point fully cover the local development scenario.

[ialidzhikov]

/assign @Kostov6