Fix fetchPriority name for React

[timothymiller]

Is there an existing issue for this?

• [X] I have searched the existing issues

Do you want this issue prioritized?

• [ ] Yes, I have sponsored
• [X] Not urgent

Current Behavior

This warning message is logged to the console when starting a next.js application:

Warning: React does not recognize the `fetchPriority` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `fetchpriority` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
    at img
    at className (webpack://next-app/src/client/image-component.tsx?51e1:212:5)
    at RouterContext (webpack://next-app/src/client/image-component.tsx?51e1:372:5)
    at SolitoImage (webpack://next-app/src/image/expo/image.web.tsx?feeb:19:5)

Expected Behavior

No warning message

Steps To Reproduce

No response

Versions

- Solito: 4.2.2
- Next.js: 14.2.3
- Expo: 51.0.9
- React Native: 0.74.1

Screenshots

No response

Reproduction

No response

[nandorojo]

open to a PR!