Chore: Remove redundant intersection type (#52453)

### What?
The type definition of `ImgProps` is the following:
```typescript
export type ImgProps = Omit<ImageProps, 'src' | 'alt' | 'loader'> & {
  loading: LoadingValue
  width: number | undefined
  height: number | undefined
  style: NonNullable<JSX.IntrinsicElements['img']['style']>
  sizes: string | undefined
  srcSet: string | undefined
  src: string
}
```

`ImgProps` is then used as part of the definition of the `ImageElementProps` type. For the latter, `Omit<ImageProps, 'src' | 'alt' | 'loader'>` is intersected with `ImgProps` even though the intersection with that type is already part `ImgProps`'s definition. This PR removes the redundancy.

### Why?
I was looking at how Next.js implemented it's optimized image component to create something similar for a WASM framework when I noticed this typing and got confused. I figured making a PR would be the polite thing to do.

### How?
Removed redundant part of type definition.

packages/next/src/client/image-component.tsx

@@ -44,15 +44,14 @@ type ImgElementWithDataProp = HTMLImageElement & {
   'data-loaded-src': string | undefined
 }
 
-type ImageElementProps = Omit<ImageProps, 'src' | 'alt' | 'loader'> &
-  ImgProps & {
-    unoptimized: boolean
-    placeholder: PlaceholderValue
-    onLoadRef: React.MutableRefObject<OnLoad | undefined>
-    onLoadingCompleteRef: React.MutableRefObject<OnLoadingComplete | undefined>
-    setBlurComplete: (b: boolean) => void
-    setShowAltText: (b: boolean) => void
-  }
+type ImageElementProps = ImgProps & {
+  unoptimized: boolean
+  placeholder: PlaceholderValue
+  onLoadRef: React.MutableRefObject<OnLoad | undefined>
+  onLoadingCompleteRef: React.MutableRefObject<OnLoadingComplete | undefined>
+  setBlurComplete: (b: boolean) => void
+  setShowAltText: (b: boolean) => void
+}
 
 // See https://stackoverflow.com/q/39777833/266535 for why we use this ref
 // handler instead of the img's onLoad attribute.