Feature/helmchart

[fanff]

This pull request introduces Helm charts for both the frontend and backend components of our application, alongside comprehensive documentation covering installation, configuration, and usage. This effort is aimed at streamlining the deployment process on Kubernetes environments, ensuring a more consistent and manageable release workflow.
Changes

Frontend Helm Chart: A new Helm chart for the frontend service, including customizable values for environment-specific configurations.
Backend Helm Chart: Similar to the frontend, the backend service now has its own Helm chart, facilitating independent deployments and scaling.
Unified Documentation: Added a README.md in the helm directory, detailing prerequisites, installation steps, chart customization

[harticode]

your helm charts are great and really helpful,
however, The image building approach will work locally only when the .env file is available.
which will not be the case in a ci cd pipeline.

[harticode]

if we removed these, we need to skip validation during build time in
frontend/src/env.mjs
try to build it without .env available in build time which will be the case in a ci/cd pipeline.

also with skipping validation, anything that starts with NEXT_PUBLIC, we need to pass it in publicRuntimeConfig instead of envs otherwise won't be picked up during the running time and will be undefined.

my approach was to put the build-time envs that we needed, in
publicRuntimeConfig check : runtime-configuration
we can ignore the hostname and use just /api/v1.
and then if the backend is hosted in a different host, the dev can just put the full address; (HTTP://......./api/v1)...