Enlisting a Blazor WebAssembly Standalone App in a .NET Aspire orchestration doesn't add the app to the AppHost

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

I created a Blazor WebAssembly Standalone App in VS 17.13.5 targeting .NET 9 and selected the project template option to enlist it in a .NET Aspire orchestration. The generated solution contained the standalone Blazor WebAssembly app, the AppHost project, and the ServiceDefaults project. However, it didn't add the Blazor WebAssembly app to the app host. If I manually add the project reference to the Blazor WebAssembly project and add `builder.AddProject("client");` to the AppHost project, it seems to work fine.

### Expected Behavior

I assume the Blazor WebAssembly app should be added to the AppHost so that when you run the AppHost project the Blazor WebAssembly app also starts and shows up in the Aspire dashboard.

### Steps To Reproduce

- Create a Blazor WebAssembly Standalone App project, selecting the option to Enlist in a .NET Aspire orchestration.

### Exceptions (if any)

None

### .NET Version info

9.0.201

### Anything else?

Nope