fix: docfx build

[JerrettDavis]

No description provided.

[Copilot]

Pull request overview

This PR addresses docfx build issues by resolving namespace ambiguities in two ASP.NET Core application entry points. The fix removes unused using statements and employs fully qualified type names where necessary.

• Removed using AspireDemo.Web.Components and using AspireDemo.Blog.Components directives
• Updated MapRazorComponents<App>() calls to use fully qualified type names

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
samples/ExperimentFramework.AspireDemo/AspireDemo.Web/Program.cs	Removed Components namespace import and used fully qualified name for App component to resolve docfx ambiguity
samples/ExperimentFramework.AspireDemo/AspireDemo.Blog/Program.cs	Removed Components namespace import and used fully qualified name for App component to resolve docfx ambiguity

---

The changes are clean and consistent across both files. By removing the using statements that were only used once and replacing the short type reference with the fully qualified name, the code resolves potential namespace ambiguities that can occur during documentation generation with docfx. This is a valid approach that doesn't impact runtime behavior or code maintainability significantly, as the namespace is only referenced in one location per file. No issues were identified in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.