fix(cli): perform environment variable inlining in transformer to support source maps

[EvanBacon]

Why

The current environment variable inlining is an extension of the development-mode support which runs in the serializer and doesn't support caching. While the new approach is to inline environment variables during transformation of production modules that are targeting client code (which is rarely ever cached).

The purpose of this change is to ensure sourcemaps cannot be broken by performing the modification before sourcemaps are generated. This change should also enable devs to use Expo env vars for tree shaking as they'll be inlined before minification is performed.

How

• Pass a new inlineEnvVars setting which reflects the EXPO_NO_CLIENT_ENV_VARS environment variable and invalidates the transform cache.
• Add a new babel plugin which inlines EXPO_PUBLIC_ environment variables that don't exist in node_modules.
• Modify the development serializer to do nothing in production.
• Unify the custom transform settings logic a little more than before.

Test Plan

• Added new babel tests that are based on the serializer tests. These are more robust because it's easier to test transformation e2e than serialization.
• Existing e2e metro tests should cover the production cases.

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• Conforms with the Documentation Writing Style Guide
• This diff will work correctly for npx expo prebuild & EAS Build (eg: updated a module plugin).