What?

Fixed matchRemotePattern function to properly handle query strings when using new URL() objects for images.remotePatterns with wildcard patterns.

Why?

When using new URL() objects for images.remotePatterns, URLs containing query strings were incorrectly rejected even when the pattern should have matched them. For example:

// next.config.js
module.exports = {
  images: {
    remotePatterns: [
      new URL('https://avatars.githubusercontent.com/u/**/*'),
    ],
  },
}

This pattern should match https://avatars.githubusercontent.com/u/74867549?v=4, but it was failing because the function didn't distinguish between root wildcards and specific path wildcards when handling empty search parameters.

How?

1. Refactored search parameter validation logic: Added clear distinction between different types of wildcard patterns
2. Allow query strings for specific wildcard paths: Patterns like /path/** or /path/**/* now correctly allow URLs with query parameters
3. Preserve strict matching: Root wildcards (, /) and non-wildcard patterns continue to reject query strings as expected
4. Improved code maintainability: Added clear variable names and comments

Fixes #80294
Fixes #78076