[Phase 8] Add E2E path filtering for Bitrise

[kieran-osgood-shopify]

Why?

GitHub and Bitrise both need changed-file decisions.
Github uses dorny/paths-filter.
Bitrise has built in support for a regex, but its more limiting than what we have in Github actions.

The approach taken in bitrise is two prong:

1. Bitrise regex to give a coarse grain skip if only things like markdown files have changed (we know no workflows need triggering
2. If the flow passes beyond the regex, each workflow has its own changed files filter script to determine whether it has any matches, it uses an deny-allow-deny approach
   File matching:
   a. files are **implicitly ** excluded by default
   b. explicitly included files will cause the workflow to run
   c. unless there is explicit deny, in which case its excluded

What?

• .github/filters/platform-non-docs.yml moved to .ci/changed-file-filters.yml for re-use across bitrise and .github
• Adds focused scripts/changed_file_filters / scripts/lib/changed_file_filters.rb helpers for reusable changed-file filter evaluation outside GitHub Actions where we cannot use dorny/paths-filter.
• Updates the Bitrise E2E run-plan producer to use shared filter groups from .ci/changed-file-filters.yml.
• Adds a coarse Bitrise changed_files.regex trigger and uses generated E2E_BUILD_* variables to skip unrelated Bitrise workflows.

How to test

shadowenv exec -- ruby e2e/scripts/e2e_matrix_to_browserstack_run_plan validate
shadowenv exec -- ruby e2e/scripts/e2e_matrix_to_browserstack_run_plan expand --changed-file platforms/swift/Sources/Foo.swift
shadowenv exec -- ruby e2e/scripts/e2e_matrix_to_browserstack_run_plan expand --changed-file protocol/languages/typescript/src/generated/Models.ts
shadowenv exec -- scripts/changed_file_filters list --changed-file platforms/react-native/modules/@shopify/checkout-kit-react-native/src/index.ts
shadowenv exec -- ruby -e 'require "yaml"; %w[.github/workflows/ci.yml .github/workflows/package-size.yml .ci/changed-file-filters.yml e2e/config/matrix.yml e2e/bitrise.yml].each { |path| YAML.safe_load_file(path, aliases: true) }; puts "yaml ok"'
shadowenv exec -- bitrise validate --config=e2e/bitrise.yml
shadowenv exec -- /opt/dev/bin/dev check e2e-bitrise-validate

[kieran-osgood-shopify]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• [Phase 8] Add E2E path filtering for Bitrise #417 👈 (View in Graphite)
• [Phase 7] Soft-launch E2E PR checks #364 : 1 other dependent PR (#401 )
• [Phase 6] Report E2E results to GitHub #363
• [Phase 5] Run BrowserStack Maestro from E2E matrix rows #362
• [Phase 4] Build React Native iOS E2E IPA artifact #361
• [Phase 3] Build React Native Android E2E APK artifact #360
• [Phase 2] Add Bitrise E2E pipeline skeleton #357
• [Phase1] Add E2E matrix launch smoke foundation #356
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[kieran-osgood-shopify]

Suggested change

`e2e/bitrise.yml` maps pull requests to the `e2e` pipeline with `trigger_map`. The trigger uses Bitrise `changed_files.regex` as a coarse source-tree gate for Checkout Kit platform, protocol, shared filter, package, and E2E paths. Bitrise does not support the same named include/exclude filter objects as GitHub Actions, so app-level filtering is enforced by `e2e/config/matrix.yml` and `e2e/scripts/e2e_matrix_to_browserstack_run_plan` after the pipeline starts.

`e2e/bitrise.yml` maps pull requests to the `e2e` pipeline with `trigger_map`. The trigger uses Bitrise `changed_files.regex` as a coarse source-tree gate for Checkout Kit platform, protocol, shared filter, package, and E2E paths. Bitrise does not support the same named include/exclude filter objects as GitHub Actions, so `platforms` level filtering is enforced by `e2e/config/matrix.yml` and `e2e/scripts/e2e_matrix_to_browserstack_run_plan` after the pipeline starts (essentially fulfilling the same need that `dorny/paths-filter` holds in github.

[kieran-osgood-shopify]

Suggested change

	The GitHub checks are kept non-required while `E2E_STRICT=false`.
	The GitHub checks are kept non-blocking while `E2E_STRICT=false`.

[kieran-osgood-shopify]

Suggested change

Markdown and `docs/` changes are excluded by the app-level filters. A docs-only change under a coarse Bitrise trigger path can still start the lightweight run-plan workflow, but it will produce an empty run plan and skip app build, BrowserStack execution, and reporting workflows.

Markdown and `docs/` changes are excluded by the `platforms` level filters at runtime during the `e2e-produce-browserstack-run-plan` workflow. A docs-only change under a coarse Bitrise trigger path can still start the lightweight ` e2e-produce-browserstack-run-plan` workflow (~15 seconds runtime), but it will produce an empty run plan and skip app build, BrowserStack execution, and reporting workflows.

[kieran-osgood-shopify]

Debating whether we remove this and only rely on the run-plan platforms level filtering at runtime
It likely only saves us seconds in machine startup before the run_if determines the workflow shouldn't run