- Introduced `BaseImage` component that branches between native and web implementations.
    - **Native**: Utilizes `FastImage` directly.
    - **Web**: Minor adjustments made to the `onLoad` event signature for compatibility.
- Eliminated `Image/index.native.js` as both native and web components now leverage a unified high-level implementation for image loading and rendering.

(cherry picked from commit 2aa37d2)

(cherry picked from commit 19b605e)

This patch focuses on resolving issues encountered with avatar image loading, specifically addressing the challenges related to CORS (Cross-Origin Resource Sharing) errors.

Changes:
- Removed the `isAuthTokenRequired` flag from the `AttachmentModal` component in various files, including `ProfilePage.js`, `RoomHeaderAvatars.js`, and `DetailsPage.js`. This change is crucial for loading of avatar images that are hosted externally.

Rationale:
- The primary purpose of this modification is to streamline the loading process for avatars by removing the unnecessary inclusion of authentication tokens in requests for external images. This approach aligns with standard practices for handling externally hosted content and aims to enhance compatibility and performance.
- Raised a question here as whether there are cases of avatar images that need authentication: https://github.com/Expensify/App/pull/24425/files#r1404352872

This update is expected to resolve the CORS errors associated with avatar image loading, thereby improving the overall functionality and user experience in our application.

(cherry picked from commit cc49208)

(cherry picked from commit 1182c7d)

- Adapt to `expo-image` deprecation of `event.nativeEvent` usage.
- Directly use the event object as recommended.
- Ensure compatibility with components using the `onLoad` prop.

# Conflicts:
#	src/components/RoomHeaderAvatars.js
#	src/pages/ProfilePage.js