[task] Automate build of public monolith Docker image

ByteChef Docker Hub: https://hub.docker.com/u/bytechef

Tasks:
- [x] The public image for the monolith should be named `bytechef` so that it is accessible on `https://hub.docker.com/r/bytechef/bytechef` url
- [x] Rename `bytechef/kubernetes/helm/bytechef-monolith` dir to `bytechef/kubernetes/helm/bytechef`
- [x] Rename `bitnaprednost/bytechef-monolith` in `bytechef/kubernetes/helm/bytechef-monolith/values.yaml` to `bytechef/bytechef`
- [ ] Automate build using GitHub Actions
- [x] Publish image to ByteChef Docker account
- [ ] Publish `try` image(uses internal h2 database, useful for quickly trying ByteChef without a need for the external database)
- [x] Define `docker-compose.yml` file in the root - can be used for quickly running locally
- [ ] Define `application-prod.yml ` or environment variables @ivicac
- [ ] Consider using `bootBuildImage` gradle task for building `bytechef-server` image instead of having manually written Dockerfile
- https://docs.spring.io/spring-boot/gradle-plugin/packaging-oci-image.html
- https://spring.io/blog/2024/08/29/spring-boot-cds-support-and-project-leyden-anticipation
- [x] Update root README.md with steps on how to run ByteChef via `docker compose`

Note:
- When defining `docker-compose.yml file`, ensure that `.bytechef` directory is persisted as it contains a `key` file with a key used for encrypting/decrypting credentials in the `connection` table
- Separate images for SaaS and Self-Hosted versions
- We will deploy from the `release` branch and use tags for saas and self-hosted versions