fix: keep required Expo Metro config subpaths (#1728)

* fix: remove @expo/metro-config from redundant dependency check

The rule incorrectly flagged @expo/metro-config as redundant, suggesting
to use expo/metro-config instead. While expo does re-export the main entry
point, it does NOT re-export subpaths like babel-transformer.

Projects that import @expo/metro-config/babel-transformer (documented by
Expo for extending the Babel transformer) cannot use expo/metro-config/
babel-transformer as it does not exist. The suggested fix is impossible
to follow for subpath imports.

Since the static check cannot distinguish between main entry and subpath
usage, and Expo SDK upgrades keep both packages in lockstep, the version
drift risk is minimal. Removing this entry prevents false positives.

Closes #1726

Co-authored-by: Skosh <skoshx@users.noreply.github.com>

* chore: add changeset for expo/metro-config fix

Co-authored-by: Skosh <skoshx@users.noreply.github.com>

* fix: keep required Expo Metro config subpaths

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Skosh <skoshx@users.noreply.github.com>
Co-authored-by: Aiden Bai <aiden@million.dev>