[Next.js][Multi-site] Updated site resolver to prefer more specific hostname matches

[ambrauer]

Description / Motivation

More specific hostname matches should take precedence over a less specific match (i.e. with wildcards). For example, given the following site info array:

[
    {
        name: "foo",
        hostname: "*"
    },
    {
        name: "bar",
        hostname: "*.app.net"
     },
     {
        name: "baz",
        hostname: "baz.app.net"
     },
]

it would resolve the following sites for given hostname:

"foo.net" > "foo"
"bar.app.net" > "bar"
"baz.app.net" > "baz"

Testing Details

Unit tests added

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

[illiakovalenko]

Looks good to me, one case to verify below