[13.x] Correctly handle route parameters with defaults and key binding

[alaminfirdows]

Note
This PR is a follow-up to the previous discussion where @crynobone suggested that the change should be submitted against the master branch instead of the 12.x patch branch.

---

Description:
This PR fixes an issue where URL::defaults() combined with route parameters (including model key binding fields) causes positional parameter misalignment when generating URLs with route() call.

Problem:
When a route defines a parameter with a key binding (e.g., {team:slug}) and a default is set using only the parameter name (e.g., URL::defaults(['team' => 'example-team']);), the default does not correctly align with the bound field (slug).
As a result, calling route() with positional or named parameters can incorrectly assign values, producing an empty query string like <URL>?team= instead of the expected URL.

Reference: #57488

Solution:
Added a check for both named parameters and key binding fields to correctly align route parameters when generating URLs.

Example:

1. Define route with model key binding:

Route::get('{team:slug}/projects/{project}', [ProjectController::class, 'show'])
    ->name('projects.show');

2. Sets default route params from middleware:

URL::defaults(['team' => 'example-team']);

3. Route Call:

// Case 1: Positional parameter
route('projects.show', 123);

// ❌ Before:
// Exceptions: Missing required parameter for [Route: projects.show] [URI: {team}/projects/{project}] [Missing parameter: project].

// ✅ After:
// http://laravel.test/example-team/projects/123


// Case 2: Named parameters
route('projects.show', ['project' => 123]);

// ❌ Before:
// http://laravel.test/example-team/projects/123?team=

// ✅ After:
// http://laravel.test/example-team/projects/123

[taylorotwell]

Does it work if you do URL::defaults(['team:slug' => 'foo'])?

[alaminfirdows]

Does it work if you do URL::defaults(['team:slug' => 'foo'])?

Yes!

Both URL::defaults(['team:slug' => 'foo']); and URL::defaults(['team' => 'bar']); work perfectly. It also keeps the precedence of the key binding when it is defined in the route.

[taylorotwell]

No I mean does the current code on 12.x work for you if you just do ['team:slug' => 'foo']