Fix missing port value across subdomains

[bakerkretzmar]

This PR fixes #208 by ensuring that the port for the current route/request is always appended when using Ziggy's route() function, even when building a route for a different domain.

Serving an app on port 8000 and the domain ziggy.test, and given the following routes:

Route::view('/', 'home')->name('home');

Route::domain('foo.ziggy.test')->group(function () {
    Route::get('user/{id}', function () {
        return view('user');
    })->name('users');
});

In Laravel, we get this:

route('home');
// http://ziggy.test:8000

route('users', 1);
// http://foo.ziggy.test:8000/user/1

In a browser console using Ziggy, previously, we would get this:

route('home').url();
// http://ziggy.test:8000/

route('users', 1).url();
// http://foo.ziggy.test/user/1 (missing port)

This PR makes Ziggy's output match Laravel's, so that instead its output looks like this:

route('users', 1).url();
/// http://foo.ziggy.test:8000/user/1

The change that caused this issue was introduced in #75, which added support for ports. That PR and the associated tests explicitly ensured that the port was not added unless the domain of the route being generated matched the current domain exactly. It's not clear to me why this functionality was set up that way, and after some research and testing I'm pretty sure it should actually work the way this PR demonstrates, so I updated that test as well to basically do the opposite of what it did before.

This is likely a breaking change and should not be released before v1.

See #75, #74, and laravel/framework#26247.