[HOLD for payment 2022-12-20] [$500] Allow native app releases to take staging env variables into consideration

[mountiny]

Problem

In this issue #10163, we have implemented a setting toggle which will aim all the API commands to staging or production API (if in Staging App). However, this works only in desktop or web, but not in native mobile apps as the live logs shown.

The reason it does not work is that we always build the App only once for deploy. We just relabel staging release for the production one and so when building the staging App we use the production env variables causing this issue

Actual behaviour

1. On native mobile App (iOS and Android), the staging API toggle is turned on
2. The API requests are still made to production API endpoints

Expected behaviour

1. On native mobile App (iOS and Android), the staging API toggle is turned on
2. The API requests will be made to the staging endpoints same as on web app version

Why is it important

This will allow us to test staging changes with staging API at the same time.

Solution

Find a way how we can use the environment variables in native app so we can distinguish between staging and production to send the API requests to desired API endpoints.

[melvin-bot]

Triggered auto assignment to @Christinadobrzyn (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

[mountiny]

I realized we have this Staging badge or dev badge even in the native apps so we must have some way to figure that out and the withEnvironment HOC

I am not sure if we can use those in the API toggle but would be worth exploring.

[melvin-bot]

Triggered auto assignment to @MitchExpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat (External)