feat(metro-config)!: Enable inlineRequires by default

[EvanBacon]

Why

Align with upstream defaults more closely. This feature may cause unexpected behavior with global side-effects so I'm marking it as a breaking change. Users can disable the feature:

const { getDefaultConfig } = require('expo/metro-config');

const config = getDefaultConfig(__dirname);

config.transformer.getTransformOptions = async () => ({
  transform: {
    experimentalImportSupport: false,
    inlineRequires: false,
  },
});

module.exports = config;

Test Plan

• This feature isn't harmful unless the order of esm transpilation is shifted. Current tests should cover the updates here.

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).