.easignore bug

### Build/Submit details page URL

_No response_

### Summary

.easignore handles "folder_name/" as a command to exclude all folders with the name "folder_name" regardless of being in the root directory or within other folders.

### Managed or bare?

Bare

### Environment

Out put is not necessary

### Error output

[EAGER_BUNDLE] Error: Unable to resolve module ../../src/components/notifications/NotificationList from /tmp/kita/eas-build-local-nodejs/b96c4b18-1862-4b94-bf3c-55998577e2a4/build/app/(tabs)/notifications-screen.tsx:
[EAGER_BUNDLE]
[EAGER_BUNDLE] None of these files exist:
[EAGER_BUNDLE] * src/components/notifications/NotificationList(.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx|.android.mjs|.native.mjs|.mjs|.android.js|.native.js|.js|.android.jsx|.native.jsx|.jsx|.android.json|.native.json|.json|.android.cjs|.native.cjs|.cjs|.android.scss|.native.scss|.scss|.android.sass|.native.sass|.sass|.android.css|.native.css|.css|.android.svg|.native.svg|.svg)
[EAGER_BUNDLE] * src/components/notifications/NotificationList
[EAGER_BUNDLE] 2 | import { View, Text, StyleSheet, StatusBar } from 'react-native';
[EAGER_BUNDLE] 3 | // Code workaround for eager bundler resolution: explicitly point to the file
[EAGER_BUNDLE] > 4 | import { NotificationList } from '@/src/components/notifications/NotificationList';
[EAGER_BUNDLE] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

### Reproducible demo or steps to reproduce from a blank project

I failed to recreate the error but try

create a project, in the .easignore add a folder name that's not on the root of the project and test the production build. You will find that in development it works but in production metro will fail. I have failed to recreate the error. But in my case I had a notifications/ folder on the root of the project and another in src/components/notiftications/ it so happened that all my production builds failed until i removed the flag from .easignore

After the successful build even adding the flag again doesn't recreate the error.