Collapse duplicated environment configuration into a single source of truth

[phertyameen]

Description
The project currently defines two separate sets of environment variables for what is conceptually the same thing: a backend base URL and an API credential. Each set is consumed by a different one of the competing API clients described in Issue 1. This duplication makes local setup confusing (which variable actually matters?) and makes it easy for a deployment to configure one set correctly while leaving the other unset or stale.

Why this matters
Configuration drift like this is a common source of "works on my machine" bugs, since whichever client happens to be imported determines which environment variable is actually read.

Acceptance criteria

• - There is exactly one environment variable for the backend base URL and one for the API credential, used everywhere.
• - The .env.example file and any setup documentation are updated to reflect the single set of variables.
• - No component or module reads from the old, now-removed variable names.
• Priority: Medium - a hygiene and reliability issue rather than a functional break, but it directly enables a clean version of Issue Consolidate the three competing API client implementations into one #228.

[ishwariyer]

Hi, I'd like to work on this, could this be assigned to me?

[Ayomide483]

I have experience in. Configuration and rerouting , let me fix this first you . It would be done fast and neat .

[Ummi-001]

Hi, I am a full stack developer I would really like to contribute on this project, as I clearly understand what is needed to be done.

If available, please assign it to me.
ETA is in 2 hours

[grantfox-oss]

🦊 GrantFox — @Ummi-001 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #233)
2. Your PR will be reviewed by the bridgelet-org maintainers

Good luck! Track your progress on GrantFox.

[best2025j]

can i be asign on this task i deliver asap