Add implicit Parsing for System.Guid query parameters in shell navigation

### Description

It is common in applications to use Guids for Identifiers. It is also common to pass a guid as query parameter when navigating between pages. Therefore it would be nice to have implicit parsing for System.Guid query parameters in Shell just like we have for strings and integers.

Second it would also be better to throw an exception when navigation fails because a query parameter cannot be resolved.
Currently if you try to use a Guid query parameter in Shell without using the object dictionary. The app just doesn't navigate but also does not throw an exception or show any error.

### Public API Changes

None

### Intended Use-Case

Use Guids as query parameters when navigating without adding extra code.

Example:
```csharp
var id = Guid.NewGuid();

var route = $"nameof(DetailPage)?Id={id}";

await Shell.Current.GoToAsync(route, true);
```

With a viewmodel:
```csharp
[QueryProperty(nameof(Id), nameof(Id))]
public partial class DetailPageViewModel : ObservableObject
{
[ObservableProperty]
private Guid _id =;
}
```

Start by locating Shell's query-parameter resolution and navigation-failure paths, then inspect how string and integer parameters are handled alongside QueryProperty. Done means Guid query parameters work without the object dictionary, and navigation reports an error when a query parameter cannot be resolved.

Written by the indexing model from the issue text.