Split up config and secrets

[ChromaticPanic]

Description

Context
Currently, all environment variables are stored in a single .env file. This makes it harder to distinguish and manage sensitive values separately from general configuration values.

Problem Statement
We need to introduce secrets.env for sensitive credentials and config.env for general configuration variables.

Acceptance Criteria

• A secrets.env.template file is created for sensitive variables.
• A config.env file is created for non-sensitive configuration variables.
• secret.env is git ignored.
• The application can load both files and work as expected.
• Rework the way we handle secrets and config for model endpoints
• add dockerfile for local dev