[Bug]: Create Site wizard fails with dependency conflict when "Laravel Boost" is enabled

### Platform

Windows

### Operating system version

Windows 11 (25H2)

### System architecture

Windows

### Herd Version

1.28.0

### PHP Version

8.4.22

### Bug description

### Bug description
When attempting to create a brand new Laravel application using the Laravel Herd desktop GUI wizard's "Create Site" feature, selecting the option to include/enable **Laravel Boost** causes the entire site creation and installation process to fail at the very end.

Composer throws a strict dependency version locking/rollback conflict error because it tries to require a constrained version of `laravel/boost` that conflicts with the newly created site's default ecosystem components.

**Expected behavior:**
Herd should either pull the latest compatible version dynamically (`composer require laravel/boost --dev`) without pinning a conflicting framework constraint, or seamlessly pass the installation to the local Herd CLI wrapper so it completes the site setup without error.

### Steps to reproduce

### Steps to reproduce
1. Open the Laravel Herd GUI.
2. Click on the "Create Site" feature wizard.
3. Keep the default settings but make sure to check/enable the **Laravel Boost** addon option.
4. Click create/install and let the process run until the dependency resolution terminal phase triggers.

### Relevant log output

```shell
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires laravel/boost 2.0 -> satisfiable by laravel/boost[v2.0.0].
- pestphp/pest-plugin-laravel is locked to version v4.1.0 and an update of this package was not requested.
- laravel/boost v2.0.0 requires laravel/roster ^0.2.9 -> satisfiable by laravel/roster[v0.2.9].
- laravel/roster v0.2.9 requires illuminate/support ^10.0|^11.0|^12.0 -> satisfiable by illuminate/support[v10.0.0, ..., v10.49.0, v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.62.0].
- pestphp/pest-plugin-laravel v4.1.0 requires laravel/framework ^11.45.2|^12.52.0|^13.0 -> satisfiable by laravel/framework[v13.12.0, ..., v13.17.0].
- Conclusion: don't install laravel/framework v13.13.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v13.14.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v13.15.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v13.16.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v13.16.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v13.17.0 (conflict analysis result)
- Only one of these can be installed: illuminate/support[v10.17.0, ..., v10.49.0, v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.62.0, v13.0.0, ..., v13.17.0], laravel/framework[v13.12.0, ..., v13.17.0]. laravel/framework replaces illuminate/support and thus cannot coexist with it.
- Only one of these can be installed: illuminate/support[v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.62.0, v13.0.0, ..., v13.17.0], laravel/framework[v13.12.0, ..., v13.17.0]. They all replace spatie/once and thus cannot coexist.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.
INFO Application ready in [node-agent]. You can start your local development using:
```

Reproduce the failure in the Herd desktop Create Site wizard on Windows 11 with the Laravel Boost option enabled, and review the Composer dependency-resolution output. Done means a new Laravel site completes installation successfully with Laravel Boost enabled, without the dependency conflict or rollback.

Written by the indexing model from the issue text.