…from EAS fingerprint (#30332)

## **Description**

The EAS fingerprint was being invalidated by JS-only changes (e.g.
`@metamask/*-controller` version bumps, `package.json`
`scripts`/`version` edits, and JS-only yarn patches), forcing
unnecessary native rebuilds and blocking OTA updates.

This change makes the fingerprint reflect only native-relevant inputs:
- Resolves the set of packages with native code via Expo autolinking
(`yarn expo-modules-autolinking resolve` for iOS and Android), with a
safe fallback to hashing everything if resolution fails.
- Adds a `fileHookTransform` that filters `package.json` down to the
`dependencies`/`devDependencies` of native packages (plus `expo`
autolinking overrides), and excludes `.yarn/patches` for JS-only
packages.
- Removes the static `.yarn/patches` `extraSource` and the now-redundant
`.fingerprintignore`, since patch filtering is handled in the transform.

Note: the transform buffers `package.json` across streamed chunks before
parsing, since `fileHookTransform` is invoked per-chunk.

## **Changelog**

CHANGELOG entry: null

## **Related issues**

Fixes:

## **Manual testing steps**

```gherkin
Feature: EAS fingerprint excludes JS-only changes

  Scenario: JS-only dependency bump does not change the fingerprint
    Given a clean working tree
    When I run "yarn fingerprint:generate" and record the hash
    And I bump a JS-only dependency version in package.json
    And I run "yarn fingerprint:generate" again
    Then the hash is unchanged

  Scenario: native dependency bump changes the fingerprint
    Given a clean working tree
    When I bump a native dependency version in package.json
    And I run "yarn fingerprint:generate"
    Then the hash differs from the baseline
```