Fix Blazor WASM SDK packaging and backport fix

[captainsafia]

Changes in this PR

This PR has a couple of changes to get the dev SDK hooked up correctly and to backport a fix from the ASP.NET Core repo. Below is a guideline for the changes in the PR.

Remove BlazorWebAssembly SDK from list of bundled SDKs to ensure the version in the repo is used not a globally installed one

• https://github.com/dotnet/sdk/pull/14968/files#diff-1ea18ff65faa2ae6fed570b83747086d0317f5e4bc325064f6c14319a9c4ff67L125

Add targets for Blazor WASM SDK to solution file

• https://github.com/dotnet/sdk/pull/14968/files#diff-15adc48e2ec26a16c1b83f53f5e4583d904fc7480c6f30e9df5a520a2a790ef1R273-R280

Fix references to tools and tasks in target file to match new layout

• https://github.com/dotnet/sdk/pull/14968/files#diff-3383a3d4e6696d707e6714511fb7e58f85a7b58319d0743047713992351f3abbL38-L39

Fixed up layout generation for tasks

• https://github.com/dotnet/sdk/pull/14968/files#diff-77ceea1be0cfda2bad0d3ad55960d8584c4cd2c684045db9df196957bf64fbcaL1

Made sure that System.CommandLine dependency was copied over into tool

• https://github.com/dotnet/sdk/pull/14968/files#diff-84643103df5f8dd13e17fb3b72d2856e69119d80656c206a8d607a5af926ef7eR193

Ensure the Blazor WASM tool is published before the SDK

• https://github.com/dotnet/sdk/pull/14968/files#diff-84643103df5f8dd13e17fb3b72d2856e69119d80656c206a8d607a5af926ef7eR184

Update test project file to ensure that project-level test targets can run

• https://github.com/dotnet/sdk/pull/14968/files#diff-bc8143061fec1517c068def5773a5325d95a226c065160c59e24ddb3e6cb16ecR1

Backport fix from dotnet/aspnetcore#28539 to the SDK here

• https://github.com/dotnet/sdk/pull/14968/files#diff-3383a3d4e6696d707e6714511fb7e58f85a7b58319d0743047713992351f3abbR466
• https://github.com/dotnet/sdk/pull/14968/files#diff-c4ff3e90606b3bcda3cd69e7cf0e61c85618bdc53fbb8e4e61065e86261e42aaR249

[wli3]

also could you update the CODEOWNERS. Instead of your name, replace it with your team's alias?

[captainsafia]

@wli3 Post-holiday bump on this PR.

[wli3]

@captainsafia also need an approval from your team member

[wli3]

@captainsafia and from now on, if you don't think a change to Blazor WASM would affect SDK, you don't need my team's approval. Since these code belong to your team in the end.