[Specs][Tests] Running tests on the repo might accidentally pick up local ENV vars

[AliSoftware]

New Issue Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read docs.fastlane.tools
• I searched for existing GitHub issues

Issue Description

Note

This is not an issue about fastlane itself — it is not preventing fastlane to run or making it crash — but an issue about the Unit Tests (aka Specs), and only when running those fastlane tests locally.

Some of our unit tests (specs) are testing cases for when an action's parameter is not provided. But if the ConfigItem being tested by that spec/test happens to have an env_name: attribute—allowing the value of that action's ConfigItem to be provided by an ENV var instead of explicitly—then running the test on a local machine might accidentally pick up environment variables from the user running the test on their machine, making the test fail or not test what it's supposed to.

So far I've encountered the case with SENTRY_AUTH_TOKEN local env var which was messing up our upload_symbols_to_sentry_spec.rb test, and I've already fixed that specific case in #21586.
But we should probably audit our tests' codebase to check if there aren't any other specs testing cases relying on the values of some ConfigItems that could be muddied by local ENV vars, and fix all of them in a similar way (aka allow(ENV).to receive(:[]).and_return(nil))

Note that this issue only affects when running the test suite on a local machine, and does not affect CI (because the environment variables set on CI machines is predictable)

Command executed

bundle exec rspec